Skip to main content
Clarky is agent first. Its MCP server lets the AI agents and tools you already use, like Grokbot, Claude, ChatGPT, Muse, and Codex, work with your CRM directly. Ask your agent about your pipeline, look up contacts, log a call, or prepare an email draft without leaving the chat. It is the same brain as Ask Clarky, available everywhere MCP is supported. Clarky implements the newest MCP specification (the 2026-07-28 revision) and remains backwards compatible with clients on earlier versions of the protocol.
Plan availability: Standard or higher (included with API Access). See Plans & Billing.

What your AI tools can do

Once connected, your AI tool has live access to this workspace’s CRM:
  • Contacts and companies: search, filter by tags or lead source, and pull full contact details
  • Pipeline: stage summaries, deal values, and moving cards between stages
  • Analytics: contact counts, deal totals, conversations, bookings, and form submissions over any date range
  • Bookings and meetings: upcoming and past meetings
  • Conversations and activities: chat, email, text, and voice history plus logged notes, calls, and tasks
  • Drafts: prepare email, text, and sequence drafts to review and send inside Clarky
AI tools can never send emails or texts through the MCP connection. Drafts always come back to Clarky, where you review and click Send yourself.

Connect a personal AI agent

Grokbot, Claude Duet, ChatGPT Dots, and Muse can all work in your workspace. Open Settings > MCP Server in Clarky, copy the prompt shown there, and send it to your agent:
1

Send the prompt

Paste the prompt into a chat with your agent. Some agents add the server straight from the chat. Others ask you to add Clarky as a custom connector in their settings, using the same server URL.
2

Sign in to Clarky

When the agent asks you to sign in, log in with your normal Clarky account and pick the workspace you want to connect.
3

Choose the access level

Leave Read and write ticked if you want the agent to log activity, update contacts, and move deals. Clear it for a read only connection.
Each agent has its own setup screens, and they change often. If the prompt alone does not work, look for a custom connector or MCP server option in your agent’s settings and paste the server URL there.

What to ask

Not sure where to start? Ask your agent “What can you do in Clarky? Show me a few examples using my own data.” Or try one of these:
  • “Who are my most recent leads?”
  • “Give me a pipeline summary”
  • “Which deals are at risk of stalling?”
  • “Log the call I just had with Jane, 15 minutes, she wants a quote”
  • “Draft a follow-up email to my most recent lead”
  • “How are my sequences doing?”
  • “Find 10 owners of roofing companies in Tampa”
You can find more examples, and the full list of tools your agent has, by clicking What can agents do? on the Agent Activity screen. Click any prompt there to copy it.

Watch your agent work

Open Activity in the Clarky sidebar. It opens on Agent Activity, a live timeline of everything connected agents do in your workspace:
  • Each request appears as a card the moment it starts, for example “Grokbot searched contacts”, and fills in with what came back
  • Click a card to see the details the agent passed and the records it got back, with links to each contact, company, or deal
  • Anything that changes your CRM carries a write tag
  • Filter by agent, or show failed requests only
People Activity, the feed of what your contacts and team are doing, is the second item under Activity. See Activity Logging.

Connect Claude (claude.ai and Claude Desktop)

1

Add a custom connector

In Claude, open Settings, then Connectors, and choose Add custom connector. Paste your server URL: https://clarky.ai/api/mcp
2

Sign in to Clarky

Claude opens a Clarky sign-in page. Log in with your normal Clarky account and pick the workspace you want to connect.
3

Approve access

Review the requested access and click Allow. Claude can now use your CRM in any conversation.

Connect Claude Code

Run this in your terminal:
Then run /mcp inside Claude Code to sign in to Clarky.

Connect Codex

Connect with an API key instead

For headless or shared setups where a sign-in flow is inconvenient, use a workspace API key as the bearer token. Create one in Settings under MCP Server, then:
Read-only keys are a good fit for shared or automated setups: the AI can look things up but cannot change pipeline stages or log activities.

Managing connections

The MCP Server section in Settings shows every AI tool connected to your workspace, who connected it, and when it was last used. Disconnect any of them at any time; the tool will need to sign in again to regain access. API keys are managed separately in the API Keys section. Access also ends automatically when a user is removed from the workspace.

Tips for better answers

  • Ask your AI tool to call get-crm-context first when a question mentions tags, pipeline stages, or lead sources by an approximate name. It returns the exact values in your workspace.
  • If your workspace has more than one agent, mention which agent’s CRM you mean, or ask for list-agents to see the options.