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:
- Go to Settings → Integrations and find Claude
- Click Add to Claude. Claude opens with dialnote already filled in
- Click Connect and sign in with your dialnote account
Or from Claude:
- Open Claude's connector settings (claude.ai/customize/connectors) and choose Add custom connector
- Enter the name
dialnoteand the URLhttps://api.dialnote.com/mcp - 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?"
Stop the approval prompts
Claude asks for approval before each tool call by default. Every dialnote tool is read-only, so you can set them to Always allow in the connector's settings.
Claude Code#
Add the server from your terminal:
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:
| Resource | Read | Notes |
|---|---|---|
| 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 |
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
Use a read-only key
Create a read-only dn_live_ key in Settings → API Keys (admins only, on the Business and Pro plans). Signing in from Claude or Claude Code doesn't need a key. 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. Write attempts with a read-only key come back as 403 INSUFFICIENT_PERMISSIONS.
Clients with native remote-URL support, like Cursor, connect directly:
{
"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:
{
"mcpServers": {
"dialnote": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.dialnote.com/mcp",
"--header",
"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 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.
Next Steps#
- Create a read-only API key for clients that can't sign in
- Set up webhooks to push call events out to your systems
- Browse all integrations
The full list of tools dialnote connects to is on the integrations page.