MCP

Connect AI assistants to dialnote over MCP: let Claude or other tools read your calls, contacts, and transcripts through a standard protocol.

MCP (Model Context Protocol) is a standard way for AI assistants to call your tools and data. Instead of copying call notes into a chat by hand, the assistant connects to dialnote directly and reads what it needs, when it needs it.

The dialnote MCP server is live and hosted at https://api.dialnote.com/mcp. There's nothing to install. You add dialnote as a connector in your AI assistant and sign in with your dialnote account. Access is read-only: the assistant can't send a message, place a call, or change or delete anything, even if asked.

Add dialnote to Claude#

Works in Claude on the web, Claude Desktop, and the Claude mobile apps. Connectors you add in one appear in the others.

From dialnote:

  1. Go to Settings → Integrations and find Claude
  2. Click Add to Claude. Claude opens with dialnote already filled in
  3. Click Connect and sign in with your dialnote account

Or from Claude:

  1. Open Claude's connector settings (claude.ai/customize/connectors) and choose Add custom connector
  2. Enter the name dialnote and the URL https://api.dialnote.com/mcp
  3. Click Connect and sign in with your dialnote account

To use it, start a chat, make sure dialnote is turned on in the chat's tools menu, and ask something like "Which calls did I miss this week?"

Claude Code#

Add the server from your terminal:

bash
claude mcp add --transport http dialnote https://api.dialnote.com/mcp

Then run /mcp inside Claude Code, choose dialnote, and sign in with your dialnote account in the browser window that opens.

What the Assistant Can Read#

Once connected, the assistant can read the following for your active dialnote organization:

ResourceReadNotes
Call Logs✓Duration, direction, status, AI summary, and tags per call. Filter by status (like voicemail or missed), direction, and date range
Call Transcripts✓The transcript, AI summary, and tags for a call
Recordings✓Recording info and metadata
Contacts✓List, get, and search by name, company, phone, or email
Contact Custom Properties✓Custom field definitions for contacts
Contact Notes✓Notes on a contact
Conversations✓List and get
Messages✓Message history (sending is a write)
Conversation Notes✓Notes on a conversation
Inboxes✓Your numbers and messaging channels
AI Agents✓Your AI agents and their knowledge bases
Reports✓Call stats and disposition summaries
Team✓Your organization's members

Example Questions to Ask#

Once dialnote is connected, ask in plain English. The assistant picks the right data on its own:

  • "Which calls did I miss this week, and who were they from?"
  • "Summarize every call with Acme this month and list anything we promised."
  • "Which voicemails came in yesterday? Give me a one-line summary of each."
  • "Which text conversations are still unread, and who are they assigned to?"
  • "How many calls did we take last week, and how did that compare with the week before?"
  • "What does our AI agent's knowledge base say about our cancellation policy?"
  • "Find every contact at Northwind and show their most recent call."

Disposition summaries need disposition codes, which come with the Business plan and up.

Other Clients and Scripts (API Key)#

Clients that can't sign in with an account, and your own scripts, can connect with a read-only dn_live_ key instead. Pass it in the Authorization header:

  • URL: https://api.dialnote.com/mcp
  • Auth: Authorization: Bearer dn_live_YOUR_READ_ONLY_KEY

Clients with native remote-URL support, like Cursor, connect directly:

json
{
  "mcpServers": {
    "dialnote": {
      "url": "https://api.dialnote.com/mcp",
      "headers": { "Authorization": "Bearer dn_live_YOUR_READ_ONLY_KEY" }
    }
  }
}

Clients that only run local commands use the mcp-remote bridge:

json
{
  "mcpServers": {
    "dialnote": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.dialnote.com/mcp",
        "--header",
        "Authorization: Bearer dn_live_YOUR_READ_ONLY_KEY"
      ]
    }
  }
}

What to Expect#

  • Read-only: the assistant can read your calls, transcripts, contacts, conversations, notes, and reports. It can't send, change, or delete anything.
  • One organization at a time: results come from the organization you last used in the dialnote web app. If you belong to more than one, switch organizations there to change what the assistant sees.
  • You stay in control: disconnect dialnote in your assistant's settings to revoke its access at any time. See our Privacy Policy for how connector data is handled.

Frequently Asked Questions#

Can the assistant send texts or place calls? No. The dialnote MCP server is read-only. An assistant can read your calls, transcripts, contacts, and conversations, but it can't send a message, place a call, or change or delete anything, even if you ask it to.

Which AI assistants can connect? Claude (web, desktop, and mobile) and Claude Code connect by signing in with your dialnote account. Cursor and any other MCP client can connect with a read-only API key, directly or through the mcp-remote bridge.

Do I need an API key? Not for Claude or Claude Code: you sign in with your dialnote account. Other clients need a read-only dn_live_ key, which admins create on the Business and Pro plans.

Whose data does the assistant see? Only your active dialnote organization: the one you last used in the web app. It sees the same data your account can see there.

How do I disconnect? Remove dialnote in your assistant's connector settings. Access stops right away. If you used an API key, delete it in Settings → API Keys.

Next Steps#

The full list of tools dialnote connects to is on the integrations page.