Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@TelePath PSTN MCP dial +1 (212) 888-1843"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
通过 AI 助手控制 TelePath 进行 PSTN 电话呼叫。
npm install在 Cursor 或 Claude Desktop 的 MCP 配置中添加:
{
"mcpServers": {
"telepath": {
"command": "node",
"args": ["/path/to/telepath-mcp-server.js"],
"env": {
"TELEPATH_USERNAME": "your_username",
"TELEPATH_PASSWORD": "your_password"
}
}
}
}在 AI 对话中直接说:
"拨打 +1 (212) 888-1843"
"我有哪些可用的电话号码？"
"新增一个电话号码"
"挂断电话"
Related MCP server: AgentPhone MCP Server
工具 | 说明 |
| 📞 拨打电话 |
| 📴 挂断通话 |
| 📱 查看电话列表 |
| 📊 查看通话状态 |
| ➕ 新增电话号码 |
| 🗑️ 删除电话号码 |
| 🛑 停止服务 |
⚠️ 同一 Board 最多同时注册 3 个电话号码
电话号码格式: +1209888xxxx (随机生成)
推荐环境: XMR-UP-XMN
详细技术文档请参阅 TEC.md
Node.js 18+
Chrome 浏览器 (Puppeteer 自动下载)
TelePath 账号
✅ 通过 API 创建随机号码可正常注册和拨打 ✅ 成功拨打真实外部号码 (+12128881843) ✅ 删除电话 API 工作正常
MIT
⚠️ TelePath 未配置。请设置环境变量：
TELEPATH_USERNAME: 你的用户名
TELEPATH_PASSWORD: 你的密码
配置方式：
在 MCP 配置中添加 env
或在 shell 中 export 环境变量
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility for disclosing behavior. It communicates that the tool surfaces setup instructions, but it doesn't explicitly state that the tool performs no configuration itself or describe the output format. The instructional tone implies it's informational, but this could be more explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and well-structured, using a warning icon, bulleted list of environment variables, and numbered configuration steps. Every element serves a purpose, and the most critical information (missing configuration) is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a setup-help tool with no parameters, no output schema, and no annotations, the description fully covers the necessary context: the problem, the specific environment variables needed, and two ways to set them. It is self-contained and complete for its intended use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the schema is empty. According to the rubric, 0 params earns a baseline score of 4. The description adds no parameter details simply because there are none to explain.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool's purpose: addressing TelePath not being configured and instructing the user to set environment variables. It names the specific resources (TELEPATH_USERNAME, TELEPATH_PASSWORD) and provides actionable steps, making the intent unambiguous even without sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly defines the context in which this tool is relevant: when TelePath is unconfigured. It lists two concrete configuration methods, giving the agent and user clear usage guidance. While it doesn't mention alternatives or exclusions, the absence of siblings makes this acceptable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.2.0telepath_setup_helpScored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose as a setup/help guide is clear, though it is not a domain operation.
A single tool cannot exhibit inconsistency. The name telepath_setup_help follows a clear snake_case convention, which is acceptable.
The server is named 'TelePath PSTN MCP' but exposes only a setup help tool, not a single actual PSTN operation. This is a severe under-scoping for the apparent domain.
The tool surface is almost empty. There are no tools for making calls, managing numbers, or any other PSTN functionality. The setup help tool does not contribute to the server's intended purpose.
Give AI agents a phone number. Voice calls, SMS, and phone number management for MCP clients.
Give AI agents secure access to RevDesk calling, SMS, phone numbers, caller IDs, and usage.
Give AI agents a phone layer for consent-based calls, transcripts, summaries, and outcomes.
Give your AI a real phone: place calls, send SMS, fetch recordings and transcripts. Local or hosted.
