MCP server
Let Claude or another AI assistant work in your Chatzyn workspace: triage and assign chats, manage templates and flows, preflight broadcasts and run store automations.
At a glance
- Endpoint:
https://chatzyn.com/api/mcp - Transport: Streamable HTTP. One JSON-RPC message per request; batches are refused.
- Sign in: with OAuth (your app opens a Chatzyn sign-in and asks you to approve), or with an API key sent as
Authorization: Bearer czk_…. OAuth apps identify themselves (Client ID Metadata Documents) or register on their own (dynamic client registration), so there is usually no Client ID to paste. - Plans: API access is on Growth and Pro.
- Limits: every tool call counts as one call against your plan's monthly API allowance, and each key is rate limited.
Connect Claude (claude.ai or Claude Desktop)
Chatzyn is in the official Claude Connectors Directory: open Chatzyn in Claude and press Connect. Claude opens the Chatzyn sign-in. Sign in, pick the workspace, check the permissions it asks for, and press Allow.
Or add it by hand as a custom connector:
- In Claude, open Customize > Connectors, press + Add, then choose Add custom connector.
- Name it Chatzyn and paste
https://chatzyn.com/api/mcpas the URL. - Press Connect, sign in and press Allow.
On a Claude Team or Enterprise plan, an organization Owner adds the connector first, under Organization settings > Connectors > Add > Custom > Web. Members then connect it from Customize > Connectors.
If Claude asks for an OAuth Client ID, enter https://claude.ai/api/mcp/auth_callback and leave the Client Secret empty.
The connection works as you. It can never do more than your own role allows in that workspace, and an owner connects as admin.
Connect Claude Code
Sign in with OAuth (run /mcp in Claude Code afterwards to sign in):
claude mcp add --transport http chatzyn https://chatzyn.com/api/mcpOr use an API key instead:
claude mcp add --transport http chatzyn https://chatzyn.com/api/mcp --header "Authorization: Bearer czk_…"Connect ChatGPT
In a work workspace, your admin may need to allow custom plugins first.
- In ChatGPT on the web, open
chatgpt.com/plugins, press + and choose Add custom MCP server. - Name it Chatzyn and paste
https://chatzyn.com/api/mcpas the server URL. - Under Connection, set authentication to OAuth and leave Client ID and Client Secret empty. ChatGPT identifies itself on its own.
- Confirm the warning, press Create as a plugin and install it, then sign in to Chatzyn and press Allow when it asks. Type @ in a chat to use it.
ChatGPT asks you before it runs any tool that changes something. It has no API key option, so OAuth is the only way in.
Connect the OpenAI API (Responses API)
Pass an API key in the MCP tool's authorization field, without the word Bearer. OpenAI does not store it, so send it with every request:
{
"type": "mcp",
"server_label": "chatzyn",
"server_url": "https://chatzyn.com/api/mcp",
"authorization": "czk_…",
"require_approval": "always"
}Connect VS Code (GitHub Copilot agent mode)
Run MCP: Add Server from the Command Palette, choose HTTP, paste https://chatzyn.com/api/mcp and give it an ID. VS Code opens the Chatzyn sign-in the first time it starts the server. Or in mcp.json:
{
"servers": {
"chatzyn": {
"type": "http",
"url": "https://chatzyn.com/api/mcp"
}
}
}To use an API key instead, VS Code can prompt for it and keep it secret:
{
"inputs": [
{
"type": "promptString",
"id": "chatzyn-key",
"description": "Chatzyn API key (czk_…)",
"password": true
}
],
"servers": {
"chatzyn": {
"type": "http",
"url": "https://chatzyn.com/api/mcp",
"headers": {
"Authorization": "Bearer ${input:chatzyn-key}"
}
}
}
}Connect Cursor
Open the Customize page, or edit ~/.cursor/mcp.json (or .cursor/mcp.json in a project). With just the URL, Cursor registers itself and opens the Chatzyn sign-in:
{
"mcpServers": {
"chatzyn": {
"url": "https://chatzyn.com/api/mcp"
}
}
}One-click install link (it holds no key), to open in your browser:
cursor://anysphere.cursor-deeplink/mcp/install?name=chatzyn&config=eyJ1cmwiOiJodHRwczovL2NoYXR6eW4uY29tL2FwaS9tY3AifQ%3D%3DTo use an API key instead, add "headers": { "Authorization": "Bearer czk_…" } next to the URL.
Connect Windsurf / Devin Desktop
Add a custom server in ~/.config/devin/mcp_config.json (or .devin/mcp_config.json in a project). With just the URL it uses OAuth: sign in when prompted, or run devin mcp login chatzyn in the CLI. For an API key, add the header:
{
"mcpServers": {
"chatzyn": {
"url": "https://chatzyn.com/api/mcp",
"headers": {
"Authorization": "Bearer czk_…"
}
}
}
}Connect Gemini CLI
gemini mcp add --transport http chatzyn https://chatzyn.com/api/mcpThen run /mcp auth chatzyn in Gemini CLI to sign in with your browser. OAuth needs a browser on the same machine; over SSH or in a container, use an API key:
gemini mcp add --transport http --header "Authorization: Bearer czk_…" chatzyn https://chatzyn.com/api/mcpConnect the Gemini app
Google limits custom apps in Gemini (gemini.google.com) to some accounts: personal Google Accounts in the US, and guides report a Google AI Pro or Ultra plan is needed too. If you do not see Add a custom app, your account is not eligible yet. On a computer, open Settings & help > Connected Apps, press Add a custom app under Custom apps, paste https://chatzyn.com/api/mcp, press Next and sign in to Chatzyn. If Gemini asks for credentials under Advanced features, leave them empty.
Connect Microsoft Copilot Studio
Use an API key. In your agent open Tools > Add a tool > New tool > Model Context Protocol, name it Chatzyn, paste https://chatzyn.com/api/mcp, and set Authentication to API key, type Header, header name Authorization. When it asks for the key, paste the whole value including the word Bearer: Bearer czk_….
Connect Zed
Settings > AI > MCP Servers > Add Server > Add Remote Server and paste https://chatzyn.com/api/mcp. With no Authorization header set, Zed starts the Chatzyn sign-in on its own. Or in settings.json:
{
"context_servers": {
"chatzyn": {
"url": "https://chatzyn.com/api/mcp"
}
}
}For an API key, add "headers": { "Authorization": "Bearer czk_…" }.
Connect Cline
In cline_mcp_settings.json. Set type, or Cline falls back to the old SSE transport. Leave out headers to sign in with OAuth instead:
{
"mcpServers": {
"chatzyn": {
"type": "streamableHttp",
"url": "https://chatzyn.com/api/mcp",
"headers": {
"Authorization": "Bearer czk_…"
},
"disabled": false,
"autoApprove": []
}
}
}Connect Goose
Extensions > Add custom extension, type Streamable HTTP, endpoint https://chatzyn.com/api/mcp. Goose opens the Chatzyn sign-in. For an API key, add the Authorization header under headers.
Connect Perplexity
Custom connectors need a paid Perplexity plan. Open Settings > Connectors and add a custom remote MCP connector (if your app shows Plugins > Add custom, use that), name it Chatzyn, paste https://chatzyn.com/api/mcp, transport Streamable HTTP, authentication OAuth. In an Enterprise organization an admin adds it under Organization settings > Connectors and turns it on for members.
Connect Mistral Le Chat
Connectors > + Add Connector > Custom MCP Connector. Name it chatzyn, paste https://chatzyn.com/api/mcp and press Connect. Choose OAuth, or Bearer token and paste a czk_… key. Only admins can add connectors; on a personal plan you are the admin.
Connect Raycast
Run Install MCP Server, transport HTTP, URL https://chatzyn.com/api/mcp. Choose OAuth type Dynamic. If your version offers HTTP headers, you can instead leave OAuth off and add Authorization with the value Bearer czk_….
Connect Manus
Settings > Connectors > + Add connectors > Custom MCP > Direct configuration, transport HTTP, URL https://chatzyn.com/api/mcp, and a custom header Authorization with the value Bearer czk_….
Connect LM Studio
Use an API key. In Program > Install > Edit mcp.json:
{
"mcpServers": {
"chatzyn": {
"url": "https://chatzyn.com/api/mcp",
"headers": {
"Authorization": "Bearer czk_…"
}
}
}
}Connect n8n or Zapier
- n8n: add an MCP Client Tool to an AI Agent, endpoint
https://chatzyn.com/api/mcp, transport HTTP Streamable, authentication Bearer Auth with aczk_…key. - Zapier: Apps > + Add connection > MCP Client, server URL
https://chatzyn.com/api/mcp, transport Streamable HTTP, OAuth No, and theczk_…key as the bearer token.
Connect from your own code (Google ADK and other SDKs)
Any MCP SDK that takes a URL and headers works with an API key. Python, Google ADK:
McpToolset(connection_params=StreamableHTTPConnectionParams(url="https://chatzyn.com/api/mcp", headers={"Authorization": "Bearer czk_…"}))Keep the key in an environment variable or a secret store, never in the code.
Any other MCP client
Add https://chatzyn.com/api/mcp as a remote (Streamable HTTP) MCP server. If it supports OAuth, it finds the Chatzyn sign-in on its own. If it asks for a header, send Authorization with the value Bearer czk_….
Not supported yet: Microsoft 365 Copilot declarative agents and Gemini Enterprise custom MCP data stores. Both need an OAuth client with a client secret, which Chatzyn does not issue.
To make a key, open Settings > API & MCP, press Create a key and pick the MCP key preset: an admin key with exactly the scopes the tools need. The key is shown once, so copy it then.
Tools
| Tool | What it does | Reads or changes | Scopes | Key role | Arguments |
|---|---|---|---|---|---|
chatzyn_list_unassigned_conversations | List unassigned conversations | Reads | conversations:read | admin or higher | channelId?, olderThanMinutes?, order?, limit?, cursor? |
chatzyn_assign_agent | Assign a conversation | Changes | conversations:assign | agent or higher | conversationId, agent, note? |
chatzyn_create_or_update_flow | Create or update a flow draft | Changes | flows:write | admin or higher | flowId?, name?, draftGraph, triggerRules? |
chatzyn_publish_flow | Publish a flow | Changes | flows:publish | admin or higher | flowId, confirm |
chatzyn_trigger_broadcast_or_template | Preflight or launch a broadcast | Changes | broadcasts:send + messages:send (launch only) | admin or higher | idempotencyKey, mode?, expectedRecipients?, campaign |
chatzyn_list_templates | List WhatsApp templates | Reads | templates:read | any | status? |
chatzyn_create_template | Create a WhatsApp template | Changes | templates:write | admin or higher | whatsappAccountId?, name, language, category, headerText?, headerSample?, body?, bodySamples?, footer?, quickReplies?, urlButtons?, phoneButton?, otp?, confirm |
chatzyn_get_store_automations | Read store automations | Reads | store:read | any | none |
chatzyn_update_store_automation | Change a store automation | Changes | store:write | admin or higher | kind, enabled, channelId, templateId, variables?, storeName?, delayDays?, delayMinutes?, confirm |
chatzyn_search | Search workspace records | Reads | contacts:read, conversations:read, flows:read, broadcasts:read, store:read (the scope for the type searched) | any (flows, broadcasts: admin; orders: agent) | type, query?, filters?, limit?, cursor? |
chatzyn_get_record | Read one record | Reads | contacts:read, conversations:read, flows:read, broadcasts:read, store:read (the scope for the type read) | any (flow, broadcast: admin; order: agent) | type, id |
chatzyn_get_conversation_messages | Read a conversation's messages | Reads | conversations:read | any | conversationId, limit?, before? |
chatzyn_get_analytics | Read workspace analytics | Reads | analytics:read | admin or higher | days?, channelId? |
chatzyn_get_workspace_status | Read workspace status | Reads | conversations:read | any | none |
chatzyn_list_workspace_catalog | List workspace tags, fields, people and replies | Reads | contacts:read | any (teams, segments: admin) | kind |
chatzyn_publish_flow, chatzyn_create_template, chatzyn_update_store_automation only act with confirm: true, and chatzyn_trigger_broadcast_or_template only launches after a clean preflight of the same campaign, so your assistant has to show you the details first. Other changes, such as assigning a chat or saving a flow draft, happen as soon as the tool is called.
Scopes
A key, or a connected app, can only use the scopes it was given, and only those its role allows.
| Scope | Grants | Lowest key role | Used by |
|---|---|---|---|
contacts:read | Read contacts and their tags. | viewer | REST and MCP |
contacts:write | Create, update and delete contacts. | agent | REST only |
conversations:read | Read conversations and their message history. | viewer | REST and MCP |
messages:send | Send messages, including uploading the media they carry (all send guards still apply). | agent | REST and MCP |
templates:read | List approved message templates. | viewer | REST and MCP |
flows:read | Read flow definitions and their publish state. | viewer | MCP only |
flows:write | Create flows and save their draft graph. Does not publish. | admin | MCP only |
flows:publish | Publish a flow, making it live. | admin | MCP only |
conversations:assign | Assign or unassign conversations to workspace members. | agent | MCP only |
broadcasts:send | Preflight and launch WhatsApp broadcast campaigns (all send guards still apply). | admin | MCP only |
templates:write | Create WhatsApp message templates and submit them to Meta for review. | admin | MCP only |
store:read | Read store automation settings, abandoned-cart figures and recent store orders. | viewer | MCP only |
store:write | Switch store automations on or off and change their template (order and COD confirmation, review requests, cart recovery). | admin | MCP only |
templates:send | Send one-time passcodes to any WhatsApp number with an approved authentication template (all send guards still apply). | agent | REST only |
analytics:read | Read workspace analytics: conversation, message, lead and order figures, agent performance and campaign results. | admin | MCP only |
broadcasts:read | Read broadcast campaigns, their delivery figures and a sample of recipients. | admin | MCP only |
Key roles
| Role | What it can do |
|---|---|
| viewer | Read only. Sees only the chats given to the person who made the key. |
| agent | Can reply to and assign the chats given to the person who made the key, and add or edit contacts. |
| admin | Sees every chat, and can also publish flows and send campaigns. |
How long access lasts
- A connected app gets an access token that lasts 1 hour and is renewed on its own with a refresh token that lasts 30 days.
- However often it renews, a connection ends 90 days after you approved it. Then you connect again.
- The sign-in code that comes back to Claude works once, for 1 minute.
- An API key does not expire. It works until you revoke it.
Disconnect or revoke
- Connected apps: a workspace admin opens Settings > API & MCP > Connected apps and presses Disconnect. It stops working straight away. If you are not an admin, ask one to do it.
- API keys: a workspace admin opens Settings > API & MCP and presses Revoke on the key. It stops working straight away.
- Removing the connector inside Claude stops Claude using it. To cancel the access on our side too, an admin disconnects it here.
Your data
- A key or connection belongs to one workspace and can never reach another.
- An admin connection sees every chat. An agent or viewer connection sees only the chats given to the person who connected it, the same rule the inbox uses.
- Tools return only the workspace data the tool is for. They never return passwords, API keys, Meta access tokens or card details.
- Anything that sends to customers still follows every send rule: the 24-hour window, opt-outs, blocked contacts, approved templates and your number's health.
- Every tool call that runs is recorded in the workspace audit log: which tool, who, which key or connected app, and whether it worked.
- What a tool returns goes to your own AI app, at your request. That app's own terms cover what it does with it.