zoko-mcp
v1.1.0
Published
Read-only MCP server for integrating Zoko with AI assistants like Claude
Readme
zoko-mcp
Read-only MCP server for integrating Zoko with AI assistants like Claude.
Tools
list_templates- every approved template. No arguments.get_template- one template by its exacttemplateId.list_webhooks- every webhook on the account. No arguments.get_webhook- one webhook by its id.list_groups- every active WhatsApp group. No arguments.get_group- one group, including its participants, by id.list_customers- one page of 100 WhatsApp customers.get_customer- one customer by id, with channels, tags and assignment.
Zoko exposes no per-id endpoint for templates, so get_template filters the full list. That
call takes ~40s and returns ~1.3MB, so the list is cached in memory for an hour. Webhooks are
small and do have a per-id endpoint, so they are fetched fresh every time.
/customer allows one request per 300 seconds, so pages are cached for ten minutes. With
~1.1M customers across ~10,900 pages, listing them all is not practical - use it to sample,
and get_customer to look one up.
Setup
Get your API key from Zoko → API & Webhooks.
Claude Code:
claude mcp add zoko -e ZOKO_API_KEY=your-key -- npx -y zoko-mcpOr any MCP client, via config:
{
"mcpServers": {
"zoko": {
"command": "npx",
"args": ["-y", "zoko-mcp"],
"env": { "ZOKO_API_KEY": "your-key" }
}
}
}License
MIT © Rocktim Saikia
