MCP | dialnote Documentation

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—your AI client connects to that URL and authenticates with a read-only dn_live_ key. Because the key is read-only, writes stay blocked. The assistant can't send a message or delete a contact even if asked; those attempts come back as 403 INSUFFICIENT_PERMISSIONS.

You need a read-only key first

Create a read-only dn_live_ key in Settings → API Keys before you connect—see API Access. Always hand an AI assistant a read-only key so a stray prompt or a compromised client can't place calls or send messages.

How It Connects#

The dialnote MCP server speaks the Model Context Protocol over Streamable HTTP. Your client connects to the hosted URL and passes your read-only key in the Authorization header:

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

No package, no install, no OAuth. Clients that support remote MCP URLs natively connect straight to that URL. Clients that only run local commands (like Claude Desktop) use the mcp-remote bridge to reach it.

Claude Desktop#

Claude Desktop connects local commands, so it reaches the hosted server through the mcp-remote bridge. Add this to your Claude Desktop config:

json

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

Restart Claude Desktop and the dialnote tools show up in the client. Ask it about your contacts or recent conversations and it reads them live.

Cursor and Native Remote-URL Clients#

Cursor and other clients with native remote-URL support connect to the hosted server directly—no bridge needed:

json

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

Quick test with MCP Inspector

To check your key and the connection before wiring up a client, run npx @modelcontextprotocol/inspector, set the transport to Streamable HTTP, enter the URL https://api.dialnote.com/mcp, add a header Authorization: Bearer dn_live_…, click Connect, then List Tools.

What the Assistant Can Read#

Once connected, the assistant can read the same resources a read-only key allows:

Resource	Read	Notes
Contacts	✓	List and get
Conversations	✓	List and get
Call Logs	✓	Duration, direction, status
Conversation Notes	✓	Notes on a conversation
Contact Notes	✓	Notes on a contact
Messages	✓	Message history (sending is a write)
Recordings	✓	Recording URL and metadata

What to Expect#

Read-only today — the assistant can read contacts, conversations, call logs, notes, messages, and recording metadata.
Writes are a later step — write tools (like sending a message) would need a full-access key and will be a separate, confirmation-gated feature. They aren't part of the read-only MCP setup.

Next Steps#

Create a read-only API key to connect with
Set up webhooks to push call events out to your systems
Browse all integrations