原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Plivo

✓ Brand-named GitHub · github.com/plivo

作者:plivo版本 1.0.0i★ 1i在云端运行官方网站 ↗
注册名称io.github.plivo/mcp

安装方法

What it does

Send SMS and WhatsApp messages, make calls and manage phone numbers on your Plivo account.

  • Connects 在云端运行
  • Account or key Sign in to the service when you connect (OAuth)
  • Category 聊天与邮件

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-11-17

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 5/5 项(仅展示,不用于排序)

安装

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

用一句话让 AI 帮你安装

请帮我安装 Plivo。按照 https://mcp.popnx.com/i/plivo-mcp.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.plivo.com) · ✓ 命令已检查 2026年11月18日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Plivo
    Remote MCP server URL · 地址https://mcp.plivo.com/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsPlivo

  4. 试一试

    用 Plivo 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Plivo,或回答中出现 Plivo 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Plivo
    Connection · 地址https://mcp.plivo.com/mcp
  3. 在聊天中选择 Plivo

    开启新聊天,输入前先从插件列表中选择 Plivo

  4. 试一试

    用 Plivo 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Plivo,或回答中出现 Plivo 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user plivo https://mcp.plivo.com/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Plivo 在列表中并显示已连接

  4. 试一试

    用 Plivo 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Plivo,或回答中出现 Plivo 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Plivo 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Plivo,或回答中出现 Plivo 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Plivo 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Plivo,或回答中出现 Plivo 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp.plivo.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Plivo 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user plivo https://mcp.plivo.com/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "plivo": {
      "url": "https://mcp.plivo.com/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "plivo": {
      "type": "http",
      "url": "https://mcp.plivo.com/mcp"
    }
  }
}

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

一览

每周下载量i
不在 npm/PyPI 上
许可证i
Apache-2.0
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.0.0
发布到注册中心i
2026年11月18日
代码最后更新i
2026年11月18日
最近检查
2026年11月18日
作者
plivo
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 plivo 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • ✓ 通过

    端点有响应

    在 266 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/plivo-mcp.svg)](https://mcp.popnx.com/en/servers/plivo-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

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

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

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

常见问题

Plivo 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(1.0.0)于昨天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

作者:anypost广泛使用↓ 5432/周★ 13945天前更新

电脑或云端✓ 服务方 · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

作者:infobip起步阶段★ 3613个月前更新

在云端运行✓ 服务方 · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

作者:w1ne起步阶段★ 3523天前更新

在云端运行✓ 服务方 · kernelcad.com
与相似项目对比
本项
Plivo
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
运行位置在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否是否
基础检查5/55/54/44/44/44/4
许可证Apache-2.0MITAGPL-3.0Apache-2.0MITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Plivo MCP server

The hosted Model Context Protocol server for the Plivo API, served at mcp.plivo.com. Claude, ChatGPT, Cursor and other MCP clients connect to one URL; nothing is installed.

It runs as a stateless Cloudflare Worker. It never holds Plivo credentials: each call carries the user's scoped stk_ token to Plivo's auth proxy (/v1/proxy), which checks the token's scope and swaps in the account's Auth ID and Auth Token.

MCP client ──Bearer stk_──▶ CloudFront ──▶ this Worker ──Bearer stk_──▶ auth proxy /v1/proxy ──Basic──▶ api.plivo.com

Every call to the auth proxy also carries:

  • The Worker's own client secret (MCP_CLIENT_SECRET) in X-Plivo-MCP-Client-Key. The auth proxy honours an MCP token only beside it, so a token cannot be used around this server and its approvals (asThisServer in src/index.ts).
  • For the proxy's logs: a fresh X-Request-Id, the MCP app's User-Agent as X-MCP-Client, the connecting IP as X-MCP-Client-IP and the inbound X-Forwarded-For as X-MCP-Forwarded-For (clientHeaders in src/upstream.ts). CloudFront sits in front of the Worker, so the connecting IP is its edge and the caller's own address is only in the forwarded list.

Opened in a browser, https://mcp.plivo.com/ serves a landing page (src/landing.ts); other clients get one plain line there. Any path other than /, /mcp and the sign-in routes answers 404.

Tools

The server registers 20 tools (src/server.ts): the 9 below and 11 shortcuts.

ToolWhat it does
plivo_api_searchFind operations by intent ("send an SMS", "list calls")
plivo_api_detailsAn operation's params, path params, whether it costs money and why it needs approval
plivo_api_readCall a GET operation
plivo_api_writeCall a POST / PATCH / DELETE operation
search_docsSearch Plivo's guides and reference: how something works, Plivo XML, error codes, FAQs
diagnose_callAsk Plivo's support assistant what happened on a call, from traces the API does not expose
diagnose_messageAsk Plivo's support assistant why a message failed or what its status means
list_organizationsList the organizations the connection may use, which one is current, and the access it was given at sign-in
switch_organizationMove the connection to another of those organizations, after the user approves

Shortcuts cover the common tasks in one call: get_account, list_numbers, search_numbers, list_messages, get_message, list_calls, get_call, send_sms, make_call, buy_number, hangup_call. Each one maps to a catalog operation and takes a short list of its params (src/shortcuts.ts); types and descriptions come from the catalog, and the Worker refuses to start if a listed operation or param is missing from it. The four plivo_api_* tools reach all 140 operations in the catalog (63 GET, 48 POST, 28 DELETE, 1 PATCH); 18 cost money and 22 cannot be undone.

The diagnose tools first check that the call or message is on the account, then send only its id (and a message's channel) to the auth proxy, which asks Plivo's support assistant and streams the answer back (30 seconds to 2 minutes for a call). The assistant can file a support ticket; the result says if it did or tried (src/diagnose.ts), and for that reason the tools are not marked read-only. They need the auth proxy, so they refuse Basic auth.

What the model sees in a reply

Every reply from Plivo has its credential fields replaced with [hidden] before the model sees it, at any depth and on reads and writes alike (hideSecrets in src/upstream.ts): text under a field named like a password, passphrase, PIN, secret, token, API key, private key, bearer, JWT, authorization or cookie, a number under a password-like field, and the value beside such a name or key in a list of headers. JSON held in a text field is searched too. An endpoint read, for one, returns the SIP password. Only a value that could be a credential is hidden: cursors (next_page_token), counts (prompt_tokens), booleans, state fields (authorization_status), error reasons, JSON Schemas and the ***REDACTED*** placeholder Plivo sends for a stored agent secret all stay. A reply cut at the 1 MB limit that names a secret is not shown at all.

A write that carries [hidden] back under a secret-named field is refused, so the marker can never replace a real credential (inputError in src/validate.ts).

Reads that return text from outside the account (messages, calls, conferences, recordings, caller names, verification sessions, AI agents and their runs, and the diagnose tools) carry a note telling the model to treat that text as data, never as instructions (UNTRUSTED_NOTE in src/server.ts).

Input checks

A write is checked before the user is asked and before anything is sent (src/validate.ts); Plivo validates the rest.

  • Phone numbers must look like phone numbers: the number in a path, and the sender and destination fields of messages, calls, multi-party call participants, masking sessions, toll-free verifications and 10DLC campaign numbers. Calls also take sip: URIs, and a message sender may be a short code or an alphanumeric sender ID.
  • One message, call or multi-party call request reaches at most 10 destinations (MAX_DESTINATIONS). The delimiter param is not accepted on those requests.
  • A URL param (url, urls, media_urls, or a name ending in _url or _urls) must be https (wss for service_url), carry no username or password, and point at a public host. A URL nested inside a structured param must point at a public host too, unless its host is a template filled in when an agent runs.

Approvals

Calls that cost money or cannot be undone (costs_money / destructive in the catalog) need the user's approval, whichever tool makes them (src/confirm.ts); that includes the number and caller-name lookups, which only read. So do free writes that keep working after the token is revoked, send traffic elsewhere or act on live traffic (ASKS_FIRST in src/confirm.ts):

  • SIP endpoints, trunks, trunk credentials, IP lists and origination URIs
  • creating or changing an application, pointing a number or Powerpack somewhere new, adding a number to a Powerpack
  • creating, changing, publishing, pausing or resuming an AI agent
  • transferring a live call, pressing keypad digits on one, removing a member from a conference
  • changing the account's own details
  • registrations that carriers or regulators review: 10DLC campaign numbers, compliance links, toll-free verification

switch_organization needs approval as well.

The first call sends nothing. How the user is asked depends on the MCP app (approvalGate in src/confirm.ts):

  1. The app's own dialog. An app that supports MCP elicitation shows the action in its own dialog, and the user approves or declines there. The model sees neither the question nor the answer, so it cannot approve for the user. Anything but a clear approval sends nothing.
  2. An approval link. For any other app the Worker registers the action at the auth proxy and returns approval_required with an approval_url and a confirmation_code. The link opens a Plivo Console page where the signed-in user approves or denies; only an admin of that organization can approve. The model then calls again with the same arguments plus the code, and the Worker asks the auth proxy what the user decided (src/approvals.ts). The link and the code approve nothing by themselves.
  3. A typed code. Where there is no auth proxy to hold approvals (local development), the call returns confirmation_required with a preview and a confirmation_code. The model shows the user the action and, once they say yes, calls again with the same arguments plus the code. Here the server trusts the model to actually ask.

Every approval:

  • covers one exact request. It is bound to the method, URL and body, and to the caller's token. A changed argument needs a new approval.
  • expires after 5 minutes.
  • works once. The auth proxy records each approval the first time it is used and refuses it after that. Local development has no auth proxy to remember this, so there an approval works until it expires.
  • names the account it will run on (Auth ID and name) and is kept with that Auth ID. The account is read again when the answer arrives, and the request is sent only if the connection is still on that account. An approved request is addressed to that Auth ID rather than me, so the auth proxy itself refuses it if a switch lands after the check (the Lookup path carries no Auth ID, so there the check alone decides). A token without the account permission is named from the organizations route instead; if Plivo cannot say which account the connection is on, nothing is asked or sent.

The preview shows every field of the request; for a paid action it adds the account balance, and for a number purchase the price. It hides any field named like a password or secret, and credentials inside URLs. An action whose preview passes 8,000 characters is refused instead of being cut short.

CONFIRMATION_MODE is confirm (default; needs CONFIRM_SECRET, 32+ characters), block (refuse such actions), or allow (send them unasked; refused unless PLIVO_API_BASE is on localhost).

Organizations

A user who belongs to several organizations ticks, at sign-in, the ones the connection may use. The token starts on the sign-in organization, and the auth proxy runs every call on the token's current organization, so the other tools take no organization parameter. list_organizations lists the allowed organizations (GET /v1/proxy/mcp/organizations). switch_organization takes an Auth ID from that list, asks the user, naming both organizations, and then moves the token (POST /v1/proxy/mcp/organization). The Worker keeps nothing: it reads the current organization from the proxy on each call (src/organizations.ts). A switch applies to calls made after it returns, so a call sent alongside it may run on either organization.

A switch between an approval's question and its answer voids that approval. An organization outside the list is a plain tool error; changing the list takes a new sign-in.

Permissions

On the sign-in screen the user can set Access to Read-only or Custom instead of Full access. Custom gives each of 8 areas (Account, Phone numbers, Messages, ...) a level: No access, Read-only, or Read and write. The auth proxy stores the result as a subset of its 17 permissions (its modules, such as message.send) for the whole connection. The proxy enforces the choice; the Worker only reports it and keeps nothing about it.

  • A call the proxy refuses with errors.error: "permission_not_granted" is a plain tool error. It tells the model that nothing was done, names the area and the level the action needs (src/permissions.ts), says the user must reconnect the server and set that level, and says not to retry before then. It is not a sign-in challenge.
  • A 403 with required_module alone is a sign-in challenge: that token predates the module. The tool call gets an HTTP 403 with error="insufficient_scope", and the client signs in again.
  • list_organizations adds permissions: full access, or each area's level.
  • Before asking the user to approve an action, the Worker reads the permissions from the organizations route, alongside the account read, and refuses at once if the action's permission is off. Only the question does this: plain reads, writes that need no approval and the call that carries the answer add no request. If the proxy reports no permissions or cannot be read, the question is asked as before.
  • Tools are not hidden from tools/list.

Sign-in

MCP clients sign in with OAuth 2.1, and this Worker is the autho

只显示了开头部分;其余内容请在仓库中阅读