URL
https://mcp.heyrik.com (Streamable HTTP; https://mcp.heyrik.com/mcp works too).
Build agents
Paste https://mcp.heyrik.com into Claude, ChatGPT, Cursor or any MCP client, sign in, and the assistant can work with your whole HeyRik account — placing calls only if you allow it.
HeyRik runs a remote Model Context Protocol server at https://mcp.heyrik.com. Paste that URL into your AI app, sign in to HeyRik in the browser window that opens, and approve. Every tool calls the matching public API endpoint as your account, with the same permissions and data scoping.
https://mcp.heyrik.com (Streamable HTTP; https://mcp.heyrik.com/mcp works too).
Your whole account: agents (create, change, delete), knowledge, voices, phone numbers, calls and transcripts, campaigns, CRM leads, widgets, chat history, usage and analytics.
Send Authorization: Bearer YOUR_API_KEY. Works with Claude Code, Claude Desktop and Cursor. A key has every permission.
claude.ai, ChatGPT, Claude Desktop and Claude Code can connect without a key: you sign in to HeyRik and approve the app.
Use the HeyRik endpoint URL in your assistant's connector settings.
claude mcp add --transport http heyrik https://mcp.heyrik.com — then run /mcp → heyrik → Authenticate (or add --header "Authorization: Bearer YOUR_API_KEY").
Settings → Connectors → Add custom connector → name HeyRik, URL https://mcp.heyrik.com → Connect, then sign in and approve on the HeyRik page that opens.
Settings → Apps & Connectors → Advanced → enable Developer mode, then Create a connector with URL https://mcp.heyrik.com and OAuth authentication. Sign in to HeyRik and approve.
In ~/.cursor/mcp.json: { "mcpServers": { "heyrik": { "url": "https://mcp.heyrik.com", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
The approval page shows the app's name, where you return to, and the permissions it asks for.
Agents, voices, phone numbers, knowledge, calls (transcripts, summaries, extracted data, recording links), campaigns and credit balance.
Create, change and delete agents, knowledge, campaigns (never start them), CRM leads and widgets, and route phone numbers. Deleting always asks you first.
Place real calls, start campaigns, add campaign contacts and call CRM leads. Off by default — tick it only if you want the assistant to dial.
Read tools cost nothing. Dialling is always explicit.
place_call, start_campaign, add_campaign_contacts and call_leads dial real numbers and spend credits (about 1 credit per call minute). They run only with confirm: true and the Place calls permission.
No MCP request limit per connection; lists return up to 100 items per call (page through for more).
Campaign ingest tokens and similar secrets are never returned to the assistant.
Every approved app has its own key you can revoke.
Each approved app appears on the API keys page as “MCP: <app name>”. Revoke it there and the app loses access immediately.
Approving the same app again replaces its previous connection.