What you are installing (in plain words)
MCP lets Cursor or Claude Desktop call Zindua tools (doctor, templates, send) instead of guessing your API. You do not learn a new framework. You add a small config file, put your project API key in the environment, and chat normally.
@zindua/mcp@1.1 runs with npx. It is not an app dependency. Your Python, .NET, or PHP project stays unchanged until the assistant scaffolds a short server-side snippet.
Start here if you are a novice
1) Create a Zindua project and copy a znd_test_ key. 2) Connect email (Gmail/SMTP) and/or WhatsApp in the dashboard. 3) Create one OTP template with a {{code}} variable. 4) Install Node.js 18+ on your laptop (only for npx). 5) Add the editor config below. 6) Reload. 7) Type: Run zindua_workflow_otp for my project.
- Prefer znd_test_ while learning
- Do not npm i @zindua/mcp into your app
- Never paste live keys into chat or git
- Full UI walkthrough: zindua.run/mcp (Cursor / Claude tabs)
Cursor vs Claude
Cursor: create .cursor/mcp.json in your repo (or ~/.cursor/mcp.json). After reload, Tools & MCP should show zindua. Optional Cursor plugin adds slash commands like /zindua-ship and /zindua-doctor.
Claude Desktop: quit the app, edit claude_desktop_config.json (macOS Application Support/Claude, or %APPDATA%\Claude on Windows), paste the same mcpServers.zindua block, restart. Claude has no slash commands — ask in natural language and name the tool.
{
"mcpServers": {
"zindua": {
"command": "npx",
"args": ["-y", "@zindua/mcp@latest"],
"env": {
"ZINDUA_API_KEY": "${env:ZINDUA_API_KEY}"
}
}
}
}What to say after you are connected
First message: Run zindua_workflow_otp for my project. If it returns stopCodegen, open the setupUrl (email or WhatsApp) and fix the dashboard, then run again.
Second: Call zindua_scaffold with my stack and the recommended template slug. Apply the short files it returns.
Third (only when you confirm a recipient): Validate then send a test to me@example.com with that template. Then: Run zindua_watch_log with the logId. Live keys are blocked unless you explicitly allow forceLive.
- zindua_workflow_otp — start here
- zindua_scaffold — certified snippet
- zindua_validate_payload → zindua_send_test
- zindua_watch_log — delivered or failed + fix
From MCP to production code
MCP diagnoses and scaffolds. Production still uses your stack SDK (@zindua/sdk, zindua Python, Zindua.Sdk, zindua/sdk) on the server only. Never put the project key in a browser or mobile app.
For the clickable install UI with Cursor/Claude tabs, see the product page. For package details, see the npm README for @zindua/mcp.