Spoke Phone MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 聊天与邮件

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://spoke-phone.usefulapi.io/mcp

claude mcp add --transport http spoke-phone https://spoke-phone.usefulapi.io/mcp

{
  "mcpServers": {
    "spoke-phone": {
      "url": "https://spoke-phone.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "spoke-phone": {
      "type": "http",
      "url": "https://spoke-phone.usefulapi.io/mcp"
    }
  }
}

https://spoke-phone.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• spokephone_list_calls

  List call records (oldest first by default; pass sortOrder descending for the latest calls), with caller, direction, duration, assigned user/team and recording URLs. Filter by time window or the external party's number. Returns { meta: { next }, calls }.

• spokephone_get_call

  Get one call record by call id.

• spokephone_get_call_recording

  Get the details and download URL of one recording of a call.

• spokephone_list_call_content_analysis

  List the Enlighten AI content-analysis results (summaries etc.) stored for one call.

• spokephone_list_directory

  List or search the unified Spoke directory (users, teams, devices) with extensions and live availability. Exactly one of extension, phoneNumber or ivrKey may be used to look up an entry. Returns { meta: { next }, entries }.

• spokephone_get_directory_entry

  Get one directory entry (user, team or device) by entry id.

• spokephone_list_users

  List active Spoke users with real-time availability. Optionally filter by email address.

• spokephone_get_user

  Get one Spoke user with availability, by user id.

• spokephone_list_teams

  List Spoke teams (call groups) with their members and availability.

• spokephone_list_locations

  List the locations of the organisation.

• spokephone_get_location

  Get one location by id.

• spokephone_list_location_users

  List the users assigned to one location.

• spokephone_list_phonebooks

  List shared phonebooks (the CRM contact containers used for caller ID), each with its contacts. Use limit 0 to list phonebooks without contacts.

• spokephone_get_phonebook

  Get one phonebook and a page of its contacts. The id may also be a user's email address for that user's personal phonebook.

• spokephone_get_phonebook_contact

  Get one contact of a phonebook.

• spokephone_list_transcripts

  List call and voicemail transcripts. Filter by time window or source.

• spokephone_get_transcript

  Get one transcript by id.

• spokephone_get_transcript_segments

  Get the per-speaker segments of one transcript.

• spokephone_list_content_analysis

  List AI content-analysis results (needs the Enlighten entitlement). Filter by time, source, participant or artifact name.

• spokephone_get_content_analysis

  Get one content-analysis result by id.

• spokephone_list_webhooks

  List the webhook subscriptions of the account.

• spokephone_get_webhook

  Get one webhook subscription by id.

• spokephone_list_trunks

  List the SIP trunks that overlay a legacy PBX onto Spoke.

• spokephone_get_trunk

  Get one SIP trunk by id.

• spokephone_send_sms

  WRITE: send a real SMS to a phone number (or a group MMS to several) from a company number or from a Spoke user's conversation number. The message appears in the Spoke conversation. Confirm the recipient and text with the user first. Needs an SMS-enabled number. POST /conversatio

• spokephone_save_phonebook_contact

  WRITE: add a contact to a phonebook, REPLACING any contact there with the same contactId (other contacts are untouched). The phonebook id may be a user's email for a personal phonebook. Contacts feed caller ID. PUT /phonebooks/{id}/contacts.

• spokephone_delete_phonebook_contact

  WRITE, destructive: delete one contact from a phonebook (it stops showing in caller ID). DELETE /phonebooks/{id}/contacts/{contactId}.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 46 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 27 个工具描述，未发现针对 AI 的隐藏指令

与“聊天与邮件”中的其他服务器比较i

• 星标数多于此分类中其他 1772 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1772 个服务器的 98% 更新
• 基础检查结果等于或优于此分类中其他 1772 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{