MCP alone vs a Cursor plugin
A project-level .cursor/mcp.json gives you tools. A Cursor plugin packages those tools with OTP security rules, a guided setup skill, and slash commands so every teammate gets the same workflow.
Zindua's plugin wraps npx @zindua/mcp@latest and reads ZINDUA_API_KEY from the environment. No hardcoded keys in the repo, and no secrets pasted into the agent chat.
What you get after install
Use /zindua-doctor to check key format, project name, and email or WhatsApp readiness. Use /zindua-setup when you want a guided OTP integration path for Next.js, FastAPI, ASP.NET, or plain HTTP.
Rules keep the agent honest: API keys stay server-side, templates match real project slugs, and test keys are preferred while iterating.
- MCP tools: doctor, project, templates, send_test
- Rules for OTP and integration style
- Skill: setup-otp-guided
- Commands: /zindua-doctor and /zindua-setup
Local test before Marketplace
Open the plugin repository folder in Cursor, confirm the zindua MCP server appears under Tools and MCP, then run /zindua-doctor.
When the doctor is green for email, list templates and send a controlled test. Prefer znd_test_ keys while the agent is assisting.