Exotelmcp

Created By
exotel9 months ago
Overview

what is ExotelMCP?

ExotelMCP is a Model Context Protocol (MCP) server that facilitates seamless integration between Claude AI and Exotel's communication APIs, enabling SMS and voice calling services along with quick audio tools.

how to use ExotelMCP?

To use ExotelMCP, ensure you have the Claude Desktop App and Exotel account set up. Configure the MCP server with your Exotel credentials and use natural language commands through Claude to interact with Exotel services.

key features of ExotelMCP?

  • 📱 SMS Services: Send single, bulk, and dynamic SMS messages with DLT compliance.
  • ☎️ Voice Calling: Initiate voice calls and connect numbers.
  • 📊 Status Tracking: Real-time delivery status and callback management.
  • 🎵 Quick Audio Tools: One-click audio playback and download.
  • 🔐 Secure Authentication: Token-based authentication system.
  • 🤖 Claude AI Integration: Direct integration with Claude through MCP protocol.

use cases of ExotelMCP?

  1. Sending bulk promotional SMS messages.
  2. Initiating voice calls for customer support.
  3. Tracking delivery status of SMS messages.
  4. Playing audio files through voice commands.

FAQ from ExotelMCP?

  • Can ExotelMCP handle both SMS and voice calls?

Yes! ExotelMCP supports both SMS and voice calling services.

  • Is there a requirement for a public domain?

Yes, ExotelMCP must be hosted on a public domain with HTTPS enabled for secure communication.

  • How do I authenticate with Exotel APIs?

Authentication is done using a secure token-based system configured in the Claude desktop settings.

Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
exotel
Star
-
Language
-
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
Crevio

2 days ago