MyMCPTools
💬

Plivo MCP

Updated June 2026No commits in 16 monthsTrust grade B79/100

The Plivo MCP, built by plivo, provides SMS, MMS, and voice calls via Plivo. It is community-built and best for Communication.

Its repository has had no commits since April 2025 (16 months ago).

by plivo

No commits in 16 months

The last commit GitHub reports for this project is from April 2025. The repository is not archived and the maintainer may return, but pip install plivo-mcp installing cleanly is not evidence that it does — expect no fixes for breaking changes in the upstream API this server wraps, and check the alternatives below before you depend on it.

About

SMS, MMS, and voice calls via Plivo. Send and receive SMS messages, make outbound calls with TTS, rent phone numbers, retrieve call recordings, and build IVR systems through Plivo's communication APIs.

Trust verdict

How grades are computed →
B
Solid79/100
low confidence · 1 measured signal

Grade B (79/100, solid) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.

What was measured

  • Repository maintenance55/100 · weight 20

    The last push or release is between six and eighteen months old. — last push 2025-04-28.

  • Source verification100/100 · weight 25

    The repository URL was confirmed to resolve against the live GitHub API and is not archived.

  • Provenance65/100 · weight 10

    Community-built. That is not a mark against it — most of the ecosystem is community-built — but there is no vendor accountable for keeping it working.

  • Listing ↔ repository match100/100 · weight 5

    The listing name lines up with the linked repository varunwahi-plivo/plivo-mcp-server.

What could not be measured

These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.

  • Live MCP handshakeunknown

    No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.

  • Measured uptimeunknown

    No probe history recorded for this server yet.

  • Tool-schema stabilityunknown

    Drift is a difference between two successive checks, and this server has none recorded.

Installation

pip⚠️ Not on the registry
pip install plivo-mcp

This command will fail: plivo-mcp was not published to PyPI when we checked on August 17, 2026. Install from the repository below instead.

Categories

💬Communication

Works With

🟣Claude Desktop⚡Cursor🤖Cline

Frequently Asked Questions

What is Plivo MCP?
Plivo MCP is an MCP server built by plivo. SMS, MMS, and voice calls via Plivo. Send and receive SMS messages, make outbound calls with TTS, rent phone numbers, retrieve call recordings, and build IVR systems through Plivo's communication APIs.
Who built Plivo MCP?
Plivo MCP was built by plivo.
Is Plivo MCP free?
Yes, Plivo MCP has a free option. This MCP server is free and open-source. Check the GitHub repository for details.
How do I install Plivo MCP?
The install command commonly listed for Plivo MCP (pip install plivo-mcp) names the PyPI package plivo-mcp, which was not published to PyPI when we checked on August 17, 2026, so it will fail. Install it from source instead: https://github.com/varunwahi-plivo/plivo-mcp-server
What does Plivo MCP integrate with?
Plivo MCP integrates with Claude Desktop, Cursor, Cline.
View on GitHubVisit Website

Repo Health

Maintained

Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.

Last commit
1y ago
Install
pip
Package
plivo-mcp

Quick Info

Install Type
pip
Author
plivo
Categories
1
Integrations
3

Related Servers

💬

Slack MCP Server

The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.

Local📘
💬

Twilio MCP Server

Twilio's official MCP server, built by the Twilio Alpha team and published as @twilio-alpha/mcp, exposes the entirety of Twilio's public API surface to AI assistants over the Model Context Protocol. Rather than hand-writing tool wrappers, the server auto-generates MCP tools directly from Twilio's OpenAPI specs, so it stays in sync with new Twilio products (Voice, Messaging/SMS, Verify, Lookup, Conversations, and more) as they ship. Because a full API surface can blow past an LLM's context window, the server supports --services and --tags flags to scope which Twilio products are loaded into a given session, keeping tool lists small and relevant. Authentication uses a Twilio Account SID paired with an API Key/Secret pair (created in the Twilio Console), passed as a single credential string at launch rather than long-lived account credentials. The monorepo also ships a companion openapi-mcp-server package that can turn any OpenAPI spec into an MCP server using the same generator, useful for teams building on top of Twilio's partner or vertical APIs. Twilio's security guidance explicitly recommends against running community MCP servers alongside the official one to reduce the risk of a compromised third-party tool touching production SMS, voice, or verification workflows tied to real phone numbers and customer data.

Local✓
💬

SendGrid MCP Server

There is no official SendGrid MCP server, and that is the first thing worth knowing if you searched for one. Twilio owns SendGrid and does publish an official MCP server at twilio-labs/mcp, but that server is generated from Twilio's own Public API specs and covers none of SendGrid's v3 email endpoints — connecting it will not give an assistant a way to send an email or touch a contact list. Twilio's own developer blog acknowledges the gap by publishing a walkthrough on building a SendGrid MCP server yourself rather than shipping one. This entry therefore tracks the most established community implementation, Garoth/sendgrid-mcp (TypeScript, 29 stars), which wraps the SendGrid v3 Marketing API. Its tool surface is broader than most email servers: contact management (list_contacts, add_contact, delete_contacts, get_contacts_by_list), list management (list_contact_lists, create_contact_list, delete_list, add_contacts_to_list, remove_contacts_from_list), sending (send_email for one-off transactional mail with optional dynamic-template data, and send_to_list which creates a SendGrid Single Send against one or more list IDs), dynamic templates (create_template, list_templates, get_template, delete_template), plus get_stats, validate_email, list_verified_senders and list_suppression_groups. Those last two exist because SendGrid rejects sends from unverified senders and requires either a suppression_group_id or a custom_unsubscribe_url on a Single Send, so an agent has to look both up before it can complete a campaign. The README is explicit that only v3 APIs are supported — legacy templates will not work. Install is from source: git clone, npm install, then point your client at the built entrypoint with SENDGRID_API_KEY in the environment. Two cautions. The npm package named sendgrid-mcp is a different project (deyikong/sendgrid-mcp, 3 stars, which does offer a READ_ONLY mode) — do not assume npx installs the repo described here. And this server exposes delete_contacts, delete_list and delete_template, which are irreversible against a live marketing database; scope the API key narrowly rather than granting full access.

Local
💬

Resend MCP Server

The Resend MCP Server is Resend's official Model Context Protocol integration, letting AI assistants send and receive transactional email, manage contacts, broadcasts, and domains directly from Claude, Cursor, or any MCP-compatible client. Resend offers two ways to connect: a fully hosted remote server at mcp.resend.com (Streamable HTTP, no local install, OAuth login on first connect) that works well for Claude web/desktop and Cursor, or the same open-source code run locally via `npx resend-mcp` (published to npm as `resend-mcp`) using stdio or HTTP transport for CI, headless agents, or self-hosted setups. Authentication is either OAuth (hosted mode, browser-based) or a Resend API key passed as a Bearer token — handy for servers where a browser login isn't possible. Setup is documented for Claude Code, Claude Desktop/web, Cursor, Windsurf, Codex, and GitHub Copilot in VS Code. Typical use: ask Claude to "send a welcome email to this new signup using our verified domain" or "list contacts added to the newsletter audience this week," and the MCP server routes the request through your existing Resend account — no custom SMTP or REST integration code required. With 546+ GitHub stars, it's one of the most widely adopted first-party MCP servers in the email/transactional-messaging category.

Local✓
💬

Discord MCP Server

The Discord MCP Server (SaseQ/discord-mcp) is a Java-based Model Context Protocol integration built on JDA (Java Discord API) that turns a Discord bot into a set of tools AI assistants can call directly. It lets Claude, Cursor, and other MCP clients read and send channel messages, manage threads, create and moderate channels and categories, manage roles and permissions, look up server (guild) members, and pull message history — enabling AI-driven community moderation, automated announcements, and Discord-native workflows without hand-writing bot code. The recommended install is Docker: set DISCORD_TOKEN (from a bot registered in the Discord Developer Portal) and an optional DISCORD_GUILD_ID as environment variables, then run the saseq/discord-mcp:latest image with SPRING_PROFILES_ACTIVE=http, which exposes the MCP endpoint at http://localhost:8085/mcp for remote/HTTP-transport clients. A Docker Compose path and a stdio-transport mode are also documented for local, per-client setups like Claude Desktop. Because it wraps JDA (Spring Boot underneath), it handles Discord's gateway/rate-limit quirks for you rather than requiring a hand-rolled REST client. This is the most-starred dedicated Discord MCP implementation; other community servers like v-3/discordmcp and hanweg/mcp-discord cover similar ground with lighter Node/Python stacks if a non-JVM runtime is preferred.

Local

Sponsored

ElevenLabs

Free Tier

The leading voice AI platform. Add lifelike text-to-speech to your Claude agents via the ElevenLabs MCP server.

Try ElevenLabs free →