Run Karzoun MCP locally so Cursor's agent can call your workspace GraphQL API as tools.
Coming soon: Installing Karzoun MCP in Cursor — from app token to first tags query. (Video embed placeholder)
- App token from Developer → Apps
- GraphQL URL:
https://{subdomain}.api.karzoun.chat/graphql
Open MCP settings
Cursor Settings → MCP → Add new global MCP server
Or edit ~/.cursor/mcp.json directly.
Add the Karzoun server
{
"mcpServers": {
"karzoun": {
"command": "npx",
"args": ["-y", "@karzounchat/mcp-server"],
"env": {
"KARZOUN_API_URL": "https://YOUR_SUBDOMAIN.api.karzoun.chat/graphql",
"KARZOUN_APP_TOKEN": "YOUR_APP_TOKEN"
}
}
}
}Replace YOUR_SUBDOMAIN and paste the JWT from appsAdd (shown once).
Do not commit mcp.json if it contains real tokens. Use env vars or Cursor's secret storage where available.
Optional: limit tools
For faster startup and smaller context, expose only CRM tools:
"env": {
"KARZOUN_API_URL": "https://YOUR_SUBDOMAIN.api.karzoun.chat/graphql",
"KARZOUN_APP_TOKEN": "YOUR_APP_TOKEN",
"KARZOUN_MCP_TOOL_PREFIX": "customers"
}Restart and verify
- Cursor Settings → MCP — toggle the server off/on or click refresh
- Status should show connected with a tool count (~75 without prefix)
- In chat: "Use Karzoun to run currentUser"
Expected: JSON profile for the app's workspace user.
Karzoun also provides a guided flow at Developer → MCP setup in the web app (/developer/mcp-setup) with copy-ready config snippets.
For team repos, add .cursor/mcp.json (same schema) so everyone uses the same server name — each developer still supplies their own token via local env if preferred.
For teams that prefer not to run npx, use hosted MCP or AI app connectors (Claude.ai, Manus, ChatGPT, remote Cursor).
- AI app connectors — Cloud AI apps (Claude, Manus, ChatGPT)
- Agent patterns — Prompts that work
- How it works — Tool ↔ GraphQL mapping
- Troubleshooting — If the server stays red