Plivo MCP Server

Created By
varunwahi-plivoa year ago
Overview

what is Plivo MCP Server?

Plivo MCP Server is an implementation of the Message Control Protocol (MCP) designed for sending SMS messages through Plivo's API.

how to use Plivo MCP Server?

To use Plivo MCP Server, install the required dependencies and configure the server with your Plivo credentials. Run the server using the provided command.

key features of Plivo MCP Server?

  • Easy integration with Plivo's SMS API
  • Supports sending SMS messages programmatically
  • Configurable server settings for different environments

use cases of Plivo MCP Server?

  1. Sending bulk SMS notifications to users.
  2. Integrating SMS functionality into applications for alerts and reminders.
  3. Automating SMS responses in customer service applications.

FAQ from Plivo MCP Server?

  • What programming language is Plivo MCP Server written in?

Plivo MCP Server is written in Python.

  • Do I need a Plivo account to use this server?

Yes, you need a Plivo account to obtain your authentication credentials.

  • Is there any cost associated with sending SMS through Plivo?

Yes, sending SMS through Plivo incurs charges based on their pricing model.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
varunwahi-plivo
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago