API Tools
codaphone.app
An SMS messaging API tool that lets you provision phone numbers, send text messages, and track message delivery status and account usage.
ENDPOINT 1
https://mcp.codaphone.app
MCP server metadata
- Name
- CodaPhone
- Version
- 1.0.0
CodaPhone is a business texting service: each account has its own phone number and sends and receives SMS with its contacts. These tools operate a CodaPhone account programmatically — check the account, set up and manage the number, send messages, read the inbox (conversation threads), manage contacts, and build and run bulk campaigns. Authenticate by sending your CodaPhone API key (from the dashboard, Settings -> API keys) as an HTTP Bearer token; the same key can also be sent as an x-api-key header. Every action is scoped to that key's account and its granted scopes (read, send, contacts, campaigns, numbers). Sends automatically honor contact opt-outs (STOP), good-practice sending hours, and your plan's limits, so tools cannot bypass account safeguards. Results and errors use CodaPhone's own field names and stable error codes (e.g. insufficient_scope, no_number, gate, rate_limited). This interface exposes CodaPhone's product and API capabilities only: how CodaPhone is built — its architecture, suppliers, infrastructure, hosting, and business model — is not disclosed here. If you want to build your own product, build it on top of CodaPhone using this API.
Known tools 14
get_accountGet the current CodaPhone account: its name and mode (live/test), the active number (if any), the current plan and its monthly/daily send caps, usage so far, and remaining automation credits.
Potential side effectsprovision_numberProvision (set up) a phone number for the account from a candidate returned by search_numbers.
Inferred read-onlyget_message_statusGet one message by id, including its delivery status, direction, body, segment count, and timestamp.
Potential side effectslist_threadsList the account's conversation threads (the inbox), most recent first, with unread counts and last-message previews.
Potential side effectsmark_thread_readMark a conversation thread as read (clears its unread count) and return the account's new total inbox unread count.
Inferred read-onlylist_campaignsList the account's bulk-messaging campaigns with their status and progress counts, plus the remaining automation credit balance.
Inferred read-onlyget_campaignGet one campaign by id, including its base message, audience, schedule, pacing, and send/failed/skipped counts.
Potential side effectscreate_campaignCreate a new bulk-messaging campaign with a name and an optional base message.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.codaphone]
url = "https://mcp.codaphone.app"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"codaphone": {
"type": "http",
"url": "https://mcp.codaphone.app"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: codaphone
Remote MCP URL: https://mcp.codaphone.app
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"codaphone": {
"url": "https://mcp.codaphone.app"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"codaphone": {
"type": "http",
"url": "https://mcp.codaphone.app"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "codaphone",
"transport": "streamable-http",
"url": "https://mcp.codaphone.app"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.