Other · Remote MCP server
AgentPhone
Give AI agents real phone numbers, messages, and voice calls via MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.AgentPhone-AI/agentphone- Version
- 0.6.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-25
- Updated
- 2026-06-25
- Publisher
- AgentPhone-AI (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/AgentPhone-AI) · how
- Repository
- github.com/AgentPhone-AI/agentphone-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.agentphone.ai/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | agentphone-mcp | 0.6.0 | stdio |
How to connect AgentPhone
AgentPhone is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.agentphone.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: agentphone-mcp version 0.6.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y agentphone-mcp@0.6.0. It reads the environment variable AGENTPHONE_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agentphone": {
"command": "npx",
"args": [
"-y",
"agentphone-mcp@0.6.0"
],
"env": {
"AGENTPHONE_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| AgentObserver - Check x402 Dependencies Before PayingCheck Exa, BlockRun, OneSource, Apify and other x402 dependencies before invoking or paying. | Remote · HTTPLive check: ✗ no handshake |
| AgentosBuild and manage policy-compliant AI agents with safety enforcement and compliance checking. | Local · stdio |
| AgentPay - Pay-per-call AI Microservices34 pay-per-call AI microservices via x402, USDC on Base, no API keys. | Remote · HTTPLive check: ✓ handshake |
| AgentPay - trust routing + spend caps for x402 agentsBuyer-side trust oracle + capped sessions for x402 agents: verified_route, receipts, 17 free tools. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| AgentpmtAI agent marketplace for automated employees, workflows, skills, and tool orchestration. | Remote · HTTPLive check: sign-in required |
| AgentprofileOne profile - skills, credentials, and memory - synced to every agent tool via one MCP URL. | Remote · HTTPLive check: sign-in required |
| AgentPumpOperate the AgentPump agent economy: read the market, create, fund, and run autonomous agents. | Local · stdio |
| AgentRaaS wrapWraps any MCP server: identical write-tool calls run once, and every tool call is audit-logged. | Local · stdio |