Give AI assistants structured access to your Karzoun workspace — customers, tags, products, users, webhooks, and more — through the Model Context Protocol.
The @karzounchat/mcp-server package maps the public GraphQL API to MCP tools one-to-one. When an agent calls customers, it runs the same operation you would send from the Playground or your backend.
Package: @karzounchat/mcp-server
Source: KarzounApps/mcp-server
Coming soon: Karzoun MCP in 3 minutes — what MCP is, when to use stdio vs hosted, and a live Cursor demo. (Embed placeholder)
| Local (stdio) | Hosted (/mcp) | |
|---|---|---|
| Best for | Cursor, Claude Desktop, local dev | Backend agents, automations, SaaS workers |
| Runs as | npx @karzounchat/mcp-server on your machine | HTTP on Karzoun gateway |
| Token lives | MCP config env (your laptop) | Your server only — never the browser |
| Setup guide | Cursor · Claude Desktop | AI connectors · Hosted MCP |
- App token — Create in Developer → Apps (authentication guide)
- GraphQL URL —
https://{subdomain}.api.karzoun.chat/graphql(quickstart) - Permissions — Scope the app to the operations your agent needs
MCP is a convenience layer for AI clients. Production integrations that do not need an LLM should call GraphQL or webhooks directly.
| Step | Guide |
|---|---|
| 1 | How it works — Tools, auth, and responses |
| 2 | Pick a setup: Cursor, AI connectors (Claude, Manus, ChatGPT…), or Hosted |
| 3 | Agent patterns — Prompts that work well |
| 4 | Tool catalog — All 75+ operations |
| Variable | Required | Description |
|---|---|---|
KARZOUN_API_URL | Yes | GraphQL endpoint URL |
KARZOUN_APP_TOKEN | Yes | App JWT from appsAdd |
KARZOUN_MCP_TOOL_PREFIX | No | Limit tools (e.g. tags, customers) |
KARZOUN_MCP_MAX_RESPONSE_BYTES | No | Response cap (default: 524288) |
Older environment variable names from previous releases are still accepted as fallbacks.
- Security — Token handling and permissions
- Troubleshooting — Common MCP errors
- Developers hub — API, webhooks, playground