Connect Claude to DialSheet

What you need

• A DialSheet account on Pro ($29/month, then $19 per seat). The API and the MCP server are Pro features. On Free the consent page loads, explains that, and the Allow button stays off.
• Some recorded calls. The agent reads what Call Intelligence produced for each one: the transcript, the summary, the disposition and the next step. A call nobody answered has none of those.
• One of: claude.ai with Connectors enabled (check Settings → Connectors), Claude Desktop, Claude Code, or Cursor. Any other client that speaks MCP over HTTP with OAuth or a bearer header should work too; those four are the ones we test.

claude.ai and Claude Desktop: three clicks

1. Open Settings, then Connectors, then Add custom connector.
2. Name it DialSheet and paste https://www.dialsheet.io/api/mcp into the URL field. Leave the client ID and client secret fields empty. The server registers the client itself when Claude first knocks.
3. Click Connect. A DialSheet page opens. Sign in if you are not already, read the list of what the connector gets, and click Allow. You land back in Claude with DialSheet showing as connected.

Claude Code: one command

Create a key first under Settings → API Keys (it is shown once, so copy it), then run this in a terminal. Claude Code keeps the header for you.

claude mcp add --transport http dialsheet https://www.dialsheet.io/api/mcp \
  --header "Authorization: Bearer ds_your_key"

Type /mcp inside Claude Code to confirm it lists dialsheet with its tools. If it says unauthorized, the key was pasted wrong or the plan it belongs to is no longer Pro.

Cursor: a five-line file

Put this in .cursor/mcp.json at the root of the project you work from. Cursor reads it on start and shows the tools under its MCP settings.

{
  "mcpServers": {
    "dialsheet": {
      "url": "https://www.dialsheet.io/api/mcp",
      "headers": { "Authorization": "Bearer ds_your_key" }
    }
  }
}

The first three things to ask it

The exact recap structure, and the endpoint behind it if you would rather not use an agent at all, is in the daily recap guide.

What the agent can and cannot do

It can:

• Read every call with transcript, AI summary, disposition and next steps, filtered by day or range in your time zone.
• Find, create and update leads, notes, tasks, tags and deals, and move deals through the pipeline.
• Enroll leads in sequences, and send email and SMS from the accounts you connected.
• Import a pasted list of up to 500 leads in one go and tag them.
• Give you the day, or the team’s day if you are the org admin, as one recap.

It cannot:

• Place or answer calls, or listen while you are on one. It works after the call, from the recording.
• See a teammate’s calls unless you are the organisation admin and ask for the team recap.
• Run on the Free plan.
• Know anything about a call that was not recorded. No recording, no transcript, no summary.
• Push you a notification when a call ends. It reads when asked, or on a schedule you set on the Claude side.

Security, in plain terms

The agent is you. Every tool call runs with a key that belongs to your account and sees only what your login sees. Email goes out from your connected mailbox and SMS from your Twilio number, in your name, so the habit to build is reading a drafted message before you say send. The key never expires on its own; disconnecting means deleting it under Settings → API Keys, which takes effect on the next request. We do not train anything on your calls. What Claude retains of what it reads is set by the Claude plan you are on, not by DialSheet.

If something goes wrong

Common questions