CallNode

io.callnodePublished by callnode.ioOfficial publisherv1.0.0Updated Oct 27, 2026

Read calls and texts, send SMS/MMS and place calls from the CallNode phone numbers you choose.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

CallNode's hosted MCP server lets an assistant read calls and texts and send SMS/MMS or place calls from the CallNode phone numbers you enable.

What you can do
  • List enabled numbers and read one number's details
  • Read call history and single call records, including summaries and transcripts for calls placed through MCP
  • Read SMS/MMS history and single messages with delivery status, and poll for new inbound texts
  • Send texts and picture messages, to a number or a Phone Book contact by name
  • Place calls run by the CallNode voice agent, when calling is switched on
  • Manage the Phone Book and check prepaid balance and auto-recharge settings
When to use it
Useful when you want an assistant to work with a business phone line: reviewing call and message history, sending texts or picture messages, or placing voice-agent calls from a chat client, with per-number and per-permission control.
Requirements
Remote hosted endpoint; nothing to install. A CallNode account with a number (self-serve numbers are US and Canada local and toll-free), MCP access switched on in the dashboard, and the numbers to expose ticked. OAuth sign-in from the client; a dashboard-created token connection is offered for automations without a browser sign-in.
Before you install
Sending messages and placing calls reach real people and cannot be undone; place_call is off by default and both are marked destructive. Sends and calls are billed from your prepaid balance, and voice-agent calls add a per-minute rate. Permissions, live or test mode and an hourly send cap are chosen on the consent page; connections can be revoked in the dashboard and sign-ins lapse after 90 days. Message and caller text is treated as untrusted.

Installation

In SourceWeft

  1. Open CallNode in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.callnode%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "callnode": {
      "type": "http",
      "url": "https://mcp.callnode.io/mcp"
    }
  }
}

README

CallNode MCP server

[CallNode MCP on mcprush]

Your CallNode phone numbers, inside your AI assistant.

CallNode hosts a Model Context Protocol (MCP) server at:

https://mcp.callnode.io/mcp

Sign in to it from claude.ai, Claude Desktop, ChatGPT, Claude Code, Cursor or VS Code, then tick the numbers the assistant may use. It can then:

  • read your call and message history;
  • send texts and picture messages;
  • call or text your Phone Book contacts by name;
  • once you switch calling on, place calls that the CallNode voice agent runs.

The server is hosted by CallNode, so there is nothing to install or run. This repository holds only the connection details: client configs, the registry entry and this README.

Before you connect

  1. Create an account at https://callnode.io/signup (no credit card to start) and get a number. Self-serve numbers are local and toll-free numbers in the US and Canada.
  2. Open Dashboard → MCP Server, switch MCP access on, and tick the numbers an assistant may use. Every connection shares this one list; a number you did not tick cannot be read from or sent from.

Connect

You give the client only the server URL. It sends you to the CallNode consent page, and you approve. No token is created, and nothing secret is pasted into a file or a shell.

On the consent page you can untick permissions (sending, for example), choose a live or test connection, and set an hourly send cap. Afterwards the connection appears under Dashboard → MCP Server, and you can revoke it there at any time.

claude.ai and Claude Desktop

  1. Open Settings → Connectors and choose Add custom connector.
  2. Enter https://mcp.callnode.io/mcp as the server URL and continue. Leave the client id and secret fields empty.
  3. Claude opens the CallNode sign-in page. Log in if asked, review the numbers and permissions, and approve.
  4. Back in Claude, enable the connector in a chat.

ChatGPT

  1. Enable Developer mode under Settings → Connectors → Advanced, then choose Create.
  2. Enter https://mcp.callnode.io/mcp as the MCP server URL and pick OAuth for authentication. No client id or secret is needed, because ChatGPT registers itself.
  3. Approve on the CallNode sign-in page, then add the connector to a chat.

Claude Code

Either use .mcp.json from this repository in your project, or run this once:

claude mcp add --transport http callnode https://mcp.callnode.io/mcp

Inside Claude Code, type /mcp, pick callnode and choose Authenticate. Approve in the browser.

VS Code (Copilot agent mode)

  1. Save .vscode/mcp.json in your workspace, then start the callnode server. VS Code opens the CallNode consent page; approve.
  2. In Copilot Chat, choose Agent mode and tick the callnode tools.

Cursor

  1. Save .cursor/mcp.json in your project, or the same entry in ~/.cursor/mcp.json, then reload Cursor.
  2. In Settings → MCP the server shows Needs login. Click it and approve in the browser.

Without a browser sign-in

For automations where a browser sign-in isn't possible, create a token connection in the dashboard. The snippets for each client are at https://callnode.io/docs/mcp#clients.

Tools

Each tool is bound to a permission you grant. A connection without that permission does not see the tool at all.

ToolPermissionWhat it does
list_numbersnumbers:readThe enabled numbers, with what each can do and whether it has its own voice agent.
get_numbernumbers:readOne enabled number. Never webhook addresses, routing or credentials.
list_callscalls:readCall records on the enabled numbers, newest first. No transcripts.
get_callcalls:readOne call record, including how it ended. For calls placed through MCP: the summary, outcome and transcript.
place_callcalls:placePlace a call. The CallNode voice agent runs it from your instructions, or the number's own voice webhook does. Off by default.
list_messagesmessages:readSMS/MMS history on the enabled numbers.
get_messagemessages:readOne message, with its delivery status.
send_messagemessages:sendSend a text or picture message, to a number or to a Phone Book contact by name.
list_phone_bookphonebook:readYour Phone Book: your own lines, with their labels.
add_phone_book_contactphonebook:managePrepares an entry and returns a link. Only you can certify and save it.
remove_phone_book_contactphonebook:manageRemoves a Phone Book entry.
get_balanceaccount:readYour prepaid balance and auto-recharge settings.
get_updatesmessages:readNew inbound texts (and calls, when the connection can read calls) since the last check, with an optional wait of up to 20 seconds.

send_message and place_call are marked as actions that reach a person and cannot be undone (destructiveHint), so clients that honour tool hints ask you before running them.

Safety and limits

  • Numbers. Only the numbers you tick are visible, and no token can widen that list.
  • Same rules as the API. Sends and calls go through the same rules as the CallNode API:
    • opt-outs and STOP replies are honoured;
    • texts and calls fall inside 8am–9pm in the recipient's local time, except your own certified Phone Book lines;
    • sending numbers must be registered for messaging;
    • calls need business verification, and do-not-call lists, destination restrictions and your concurrent-call limit apply;
    • your balance must cover each send.
  • Per-connection limits:
    • 30 sends an hour by default, settable from 1 to 200;
    • an identical text to the same recipient within 60 seconds is sent once;
    • 10 calls an hour, and the same from/to pair within 60 seconds is never dialled twice;
    • 120 tool calls a minute.
  • The voice agent introduces itself as an AI assistant calling on behalf of your business and never claims to be human. It cannot transfer a call or take card details.
  • Untrusted content. Message bodies and caller-supplied text reach the assistant marked as untrusted, so a text that tries to give it instructions reads as data.
  • Activity log. Every tool call, allowed or refused, appears under Recent activity in your dashboard. Message contents are never stored there.
  • Revoking. A revoked connection is refused on its next request. A sign-in lapses after 90 days without a fresh one.
  • Test connections run every rule, then simulate the send or the call. Nothing leaves the platform and nothing is charged.

Pricing

The MCP server has no fee. Texts and calls are billed from your prepaid balance at your normal rates, and calls the CallNode voice agent runs add a per-minute rate for the voice. All rates are on https://callnode.io/pricing.

Support

Files in this repository

FileFor
server.jsonThe Official MCP Registry entry (io.callnode/mcp)
.mcp.jsonClaude Code
.vscode/mcp.jsonVS Code
.cursor/mcp.jsonCursor

These files are released under the MIT License. The CallNode service itself is covered by the CallNode Terms.

Source: README.md at commit ef50bc8

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 19, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts