Create a scoped token

  • Sign in to InstaChime and open `/settings`.
  • Find API tokens & MCP.
  • Name the token after the AI client or automation owner, such as `Ops assistant`.
  • Keep `mcp:use` enabled. It is required for every MCP call.
  • Add only the scopes the client needs: `leads:read`, `analytics:read`, `workflows:read`, or `leads:write` for controlled test leads.
  • Set an expiration date for temporary testing tokens.
  • Create the token and copy it immediately. InstaChime will not show the full value again.

Use the MCP endpoint

The production MCP endpoint is a JSON-RPC over HTTP endpoint. Send requests with the API token in the Authorization header.

https://instachime.com/api/mcp

Initialize the connection

curl https://instachime.com/api/mcp \
  -H "content-type: application/json" \
  -H "authorization: Bearer ichm_your_token_here" \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"Your AI client","version":"1.0.0"}}}'

List available tools

The tool list is filtered by token scope, so a read-only analytics token will not see write-capable tools.

curl https://instachime.com/api/mcp \
  -H "content-type: application/json" \
  -H "authorization: Bearer ichm_your_token_here" \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

Call a read-only lead tool

curl https://instachime.com/api/mcp \
  -H "content-type: application/json" \
  -H "authorization: Bearer ichm_your_token_here" \
  --data '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"instachime.leads.list_recent","arguments":{"limit":5,"status":"new"}}}'

Available tools

  • `instachime.leads.list_recent` requires `leads:read`.
  • `instachime.leads.get` requires `leads:read`.
  • `instachime.analytics.summary` requires `analytics:read`.
  • `instachime.workflows.list` requires `workflows:read`.
  • `instachime.workflows.recent_runs` requires `workflows:read`.
  • `instachime.leads.create_test` requires `leads:write` and creates one controlled test lead.

Operate safely

  • Use separate tokens per AI client or automation owner.
  • Prefer read-only scopes for assistants that summarize leads or analytics.
  • Grant `leads:write` only to clients that need a controlled test lead workflow.
  • Revoke unused tokens from `/settings`.
  • Review audit logs when a token is used by a new AI tool.
  • Do not paste tokens into public docs, screenshots, issue trackers, or frontend JavaScript.

Official references