Model Context Protocol

An MCP server for SMS and voice.

VanceTel ships a Model Context Protocol server so AI agents and Claude Code can act on your phone system in the loop — send a text, resolve a contact, check a message’s status — without you writing a custom tool layer first.

It runs alongside the REST API and webhooks, over the same platform. An agent and a human share one softphone, one thread, one contact list.

Book a demo Read the API docs

send_messagefind_contactcreate_contactget_message

claude_desktop_config.json

{
  "mcpServers": {
    "netexem": {
      "command": "npx",
      "args": ["-y", "@netexem/mcp-server"],
      "env": {
        "NETEXEM_API_KEY": "sk_live_..."
      }
    }
  }
}

Add one entry. Your agent can act on the phone system.

Definition

The VanceTel MCP server is a Model Context Protocol endpoint that lets AI agents and Claude Code act on a real phone system: send an SMS, look up or create a contact, and check a message’s status. Each tool maps to the same actions exposed by the REST API, so an agent and your own code operate on one phone system — not two copies of it.

What agents can do

Real tools, mapped to real phone actions.

Send a text from an agent

An agent sends two-way SMS from your business number with one tool call. The message routes through the REST API and lands in the shared softphone thread, so a human can pick it up.

send_message

Resolve and create contacts

Look up a contact by number or create one on the fly. The agent keeps the shared contact list current, so the next inbound call resolves with caller-ID instead of a raw number.

find_contact · create_contact

Check a message’s status

Fetch a message by id to see whether it queued, sent, delivered or failed — so an agent can confirm a send before it follows up, without polling your own store.

get_message

Pairs with REST + webhooks

The MCP server is one surface over the same platform. Agents act through MCP; your services call the REST API directly and subscribe to HMAC-signed webhooks for inbound events.

shared platform

In the loop

The agent calls a tool. A text goes out.

A tool call through the MCP server routes to the same REST endpoint your services use. The message sends from your business number and lands in the VanceTel softphone, so a human can read the thread and take over.

No second integration. No drift between what the agent did and what your code sees.

agent tool call — send_message

// The agent calls the MCP tool; the server posts to the REST API.
{
  "tool": "send_message",
  "arguments": {
    "from": "+15551234567",
    "to": "+15557654321",
    "body": "Heads up — your 2pm is confirmed. Reply STOP to opt out."
  }
}

// → POST https://api.netexem.com/v1/messages
// → { "id": "msg_01H...", "status": "queued" }
// The same text also lands in the softphone thread.

Why MCP

A standard interface beats a bespoke tool layer.

Native to Claude Code

MCP is the protocol agents already speak. Add the server to your config and the phone tools appear — no glue code to write and maintain.

One source of truth

Tools map to the same actions as the VanceTel REST API. An agent and your services act on one phone system, so behavior stays consistent.

Human in the loop

Everything an agent does surfaces in the softphone. A person can read the thread, reply, or take the conversation over at any point.

FAQ

MCP, answered.

Want to see an agent send a text live? Book a walkthrough.

Book a demo

What is an MCP server?

An MCP (Model Context Protocol) server is a standard interface that exposes tools and data to AI agents. VanceTel runs one for the phone system, so agents and Claude Code can call tools like send_message, find_contact and create_contact directly instead of you wiring custom function calls by hand.

What can agents do through the MCP server?

Agents can send a text from your business number, look up or create a contact, and check a message’s delivery status — all in the loop, while a human stays in the same softphone. Each tool maps to the same REST API actions, so what an agent does is consistent with what your own services do.

Is the MCP server separate from the REST API?

No — it is another surface over the same platform. The MCP server is built for agents and Claude Code; the REST API is built for your services; webhooks push inbound events to your endpoints. They act on one phone system, so a text an agent sends shows up in the same thread as one your code sends.

Give your agents a phone.

See the MCP server, the REST API and webhooks act on one phone system in a 20-minute walkthrough.

Book a demo Explore the docs