# Sent MCP MCP Server > **Sent MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Sent MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/sent-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Sent provides programmable customer messaging across SMS, WhatsApp, and RCS. Send personalized or template-based messages to individual or bulk recipients, schedule deliveries, manage contacts and sender profiles, check phone number validity, monitor delivery statuses, and track messaging performance and compliance requirements. --- ## Details - Server ID: `sent-mcp` - Version: 9c706d5b8e7546f27e008424a167382dc9f85d28 - Tools: 27 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Sent MCP has to be in the toolset first. In order: 1. Add Sent MCP to your toolset at https://mewcp.com/mcp/sent-mcp 2. Connect your Sent MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (27) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `account.get` _(read)_ — Returns the account associated with the calling API key (organization, user, or profile). Includes id, name, email, type, parent organization id, and creation… - `balance.get` _(read)_ — Returns the calling account's own balance row and its effective sending balance. For sender profiles, effective balance follows the billing configuration:… - `compliance.requirements` _(read)_ — Returns what a market requires before a sender can be provisioned there: the fields to supply, which are mandatory, and the names of any documents that must be… - `compliance.setup_plan` _(read)_ — Returns the exact call that sets a market up, with every compliance key the market wants already present and blank. Use this after compliance.requirements when… - `contacts.create_many` _(write)_ — Creates or restores associations between the calling customer and up to 10 contacts. Each phone number is normalized and resolved through Sent's contact index,… - `contacts.delete` _(destructive)_ — Soft-deletes only the calling customer's association with a contact. The shared contact and its channel-capability records remain in Sent. Returns false when… - `contacts.get` _(read)_ — Looks up a single contact by id. Structured output returns found plus the contact item; found is false when no contact with that id belongs to the caller. - `contacts.list` _(read)_ — Lists the calling customer's contacts with pagination. Search matches the contact's national-format phone number; the optional channel filter matches the… - `contacts.message_summary` _(read)_ — Returns the per-contact message summary: total/by-channel counts, first/last seen, and per-channel success rates. Throws when the contact does not belong to… - `dashboard.contacts` _(read)_ — Returns total contact count for the calling customer. - `dashboard.deliverability` _(read)_ — Returns the calling customer's all-time outbound deliverability percentage, rounded to two decimals. The numerator is messages in SENT, DELIVERED, or READ… - `dashboard.messages_sent` _(read)_ — Returns time-bucketed SMS and WhatsApp counts for the calling customer's outbound messages whose status is DELIVERED or READ. Presets cover 24 hours, 7 days,… - `feedback.send` _(write)_ — Sends feedback about Sent's tools to the Sent team: a missing capability, a wrong, confusing, or unexpected result, an unresolved error, or praise. Intended… - `messages.activities.list` _(read)_ — List the lifecycle activity timeline for a message (QUEUED, PROCESSED, SENT, DELIVERED, READ, FAILED, ...). Throws if the message does not belong to the caller. - `messages.get` _(read)_ — Returns a customer-safe view of one message by id, including recipient and sender, template summary, requested and resolved channels, schedule, rendered… - `messages.send` _(destructive)_ — Accepts messages for asynchronous delivery through Sent smart routing ("sent"), SMS, WhatsApp, or RCS. Sends are template-only: there is no free-form text… - `numbers.lookup` _(write)_ — Performs an external, paid, quota-consuming lookup for a phone number. Returns normalized validity plus the recipient network's carrier, line type, country,… - `onboarding.status` _(read)_ — Returns the calling customer's most recent onboarding/conversion-flow status (e.g. SIGNED_UP, KYC_COMPLETED, ONBOARDED). Structured output returns found plus… - `sender_profiles.create` _(write)_ — Creates a sender profile under the calling organization. Provisioning a dedicated sender claims a phone number and may incur registration fees, so… - `sender_profiles.delete` _(destructive)_ — Deletes a sender profile owned by the calling organization. This is destructive and affects live messaging: it can disconnect WhatsApp, release the profile's… - `sender_profiles.get` _(read)_ — Looks up one sender profile owned by the calling organization. Structured output returns found plus the profile; found is false when no profile with that id… - `sender_profiles.list` _(read)_ — Lists the sender profiles owned by the calling organization, with channel readiness for each. Profile API keys own no profiles and receive an empty list. - `sender_profiles.update` _(write)_ — Updates a sender profile's name, short name, or description. Omitted fields are left unchanged. Sending description as null clears it; name and short name… - `templates.delete` _(destructive)_ — Deletes a template the calling account owns from Sent without deleting it from Meta. LOB templates and required OPT_IN, OPT_OUT, or HELP auto-reply templates… - `templates.get` _(read)_ — Returns one template owned by the calling account by id. Structured output returns found plus the template item; found is false when the account owns no… - `templates.get_by_name` _(read)_ — Returns the newest template owned by the calling account with the given display name. Structured output returns found plus the template item; found is false… - `templates.list` _(read)_ — Lists the templates the calling account owns, with pagination and optional name, status, and category filters. Accounts are isolated: an organization's list… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)