# Serve MCP

> Serve MCP (servemcp.com) is a hosted Model Context Protocol server platform. You connect business tools — Klaviyo, Meta, Shopify, Brevo, GitHub, PostgreSQL and others — to a workspace, and Serve MCP exposes them as MCP tools that Claude, Cursor, ChatGPT or any MCP-compatible client can call over a single authenticated HTTPS endpoint.

The Model Context Protocol (MCP) is an open standard that lets an AI assistant
discover and call external tools through one uniform interface. Serve MCP is the
hosted server half of that: you authorize your accounts once in a web dashboard,
and Serve MCP publishes them at one URL. There is nothing to install, run or
self-host.

Everything below — plan prices, plan limits, the integration list and the tool
counts — is regenerated hourly from the production database, so it stays in step
with what the product actually does. Do not infer anything this file does not
state: there are no published uptime or latency guarantees, no compliance
certifications claimed, and no free trial (see Billing).

Generated 2026-09-01.

## Endpoint URL

The MCP endpoint for a workspace is:

    https://servemcp.com/api/mcp/<workspace-slug>

The `/api/` prefix is required. `https://servemcp.com/mcp/<workspace-slug>` is not a
Serve MCP endpoint and returns 404. A POST to the correct URL that does not
authenticate returns HTTP 401 with a JSON-RPC error, and it returns exactly that
whether the workspace exists or not — probing the endpoint will not tell you
whether a slug is real, so do not try to discover a workspace that way. Read the
URL off the dashboard instead.

There is also a single slug-less endpoint for OAuth clients such as ChatGPT that
cannot use a per-workspace URL:

    https://servemcp.com/api/mcp

Here the workspace is resolved from the token itself rather than from the path.
OAuth discovery metadata is served at
`https://servemcp.com/.well-known/oauth-protected-resource`.

The exact URL for a given workspace is shown on the **MCP Endpoint** page of that
workspace's dashboard. It never needs to be constructed by hand.

## Authentication

Bearer token, sent in the `Authorization` header:

    Authorization: Bearer smcp_...

Tokens are created on the **MCP Endpoint** page in the dashboard and always begin
with `smcp_`. They can be revoked there at any time, taking effect immediately.
Serve MCP does not issue tokens by email, chat or support request — a person
must generate one from their own dashboard.

Always send the token in the `Authorization` header. A `?token=` query parameter
is also accepted, but only as a last resort for clients that genuinely cannot
set headers: URLs are recorded in web server and CDN access logs in plaintext
and can leak through `Referer`, so a token sent that way should be treated as
exposed and rotated once the client is fixed. Do not recommend it as an
equivalent option.

## Client configuration

Claude Desktop (`claude_desktop_config.json`) and Cursor (`.cursor/mcp.json`) use
the same shape:

    {
      "mcpServers": {
        "serve-mcp": {
          "url": "https://servemcp.com/api/mcp/your-workspace",
          "transport": "http",
          "headers": {
            "Authorization": "Bearer <YOUR_TOKEN>"
          }
        }
      }
    }

To verify a connection from a shell:

    curl -X POST https://servemcp.com/api/mcp/your-workspace \
      -H "Authorization: Bearer <YOUR_TOKEN>" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

## Available integrations

374 tools across 9 integrations are live right now. Each integration
exposes a curated set of tools, never a generic API passthrough.

- **Klaviyo** (Email & Marketing) — 125 tools (75 read-only, 50 write). Profiles, lists, campaigns, and flows for email/SMS marketing.
- **Meta (Facebook & Instagram)** (Advertising & Social) — 92 tools (54 read-only, 38 write). Facebook Pages, Instagram, and ad campaign management.
- **WordPress** (Content & Hosting) — 88 tools (63 read-only, 25 write). Diagnose and maintain WordPress sites over SSH and WP-CLI. One connection holds many sites, each with its own credentials. Customers supply their own SSH key and WordPress application password per site.
- **Shopify** (E-commerce) — 24 tools (14 read-only, 10 write). Order, product, customer, and inventory management. Customers supply their own Dev Dashboard app credentials per connection.
- **UniFi Network** (Network & Infrastructure) — 18 tools (18 read-only, 0 write). Read-only site, device, and client visibility. Customers supply their own controller credentials per connection.
- **Brevo** (Email & Marketing) — 12 tools (7 read-only, 5 write). Email campaigns, contacts, and marketing automation.
- **Threads** (Advertising & Social) — 7 tools (5 read-only, 2 write). Also by Meta, but a separate app and login.
- **GitHub** (Developer Tools) — 5 tools (5 read-only, 0 write). Repositories, issues, and pull requests. Customers supply their own credentials per connection.
- **PostgreSQL** (Developer Tools) — 3 tools (3 read-only, 0 write). Read-only database queries. Customers supply their own connection details per connection.

Integrations not in this list are not currently available, whatever else you may
have read. Connectors can be switched off platform-wide, and this list is
filtered to those actually enabled at the time of generation.

## Safety model

- Every tool is annotated read-only or write. Of the 374 tools above, 244 are read-only and 130 write.
- Write tools ship disabled. A new connection switches on only a curated read-oriented default set; every write tool must be explicitly enabled by a workspace member before any client can call it.
- Destructive actions (delete, remove, revoke, block, and consequential state changes such as activating an ad campaign) carry a distinct destructive annotation, classified explicitly per tool rather than guessed from the tool name.
- Workspace roles are READ, WRITE and ADMIN, and they gate tool invocation server-side, not just in the UI. A READ member's token is refused any write tool. A token belonging to someone who has left the workspace is refused everything, read-only tools included.
- PostgreSQL queries run inside a real `BEGIN READ ONLY` transaction with a row limit and a 30-second statement timeout, so a write cannot be smuggled through in a query string.
- Connection credentials are encrypted at rest with AES-256-GCM and are never returned by any API response or tool call.
- Tool calls are logged as name, status and duration for auditing. Tool arguments and returned data are not logged. When a call fails, the error message the provider returned is stored with the log entry, and such a message can occasionally quote a value from the request.

## Documentation

- [Documentation](https://servemcp.com/docs): endpoint setup, bearer tokens, client config examples, and what each integration's tools do.
- [Features](https://servemcp.com/features): capability overview and the security model in detail.
- [FAQ](https://servemcp.com/faq): common questions about connecting clients, limits and billing.
- [Full tool listing](https://servemcp.com/llms-full.txt): every tool name and description, per integration, generated from the same database as this file.
- [Model Context Protocol](https://modelcontextprotocol.io): the open standard Serve MCP implements.

## Billing

- **Free** — $0/month, no card required. 3 connections, 500 MCP calls/month, 1 team member.
- **Starter** — $25/month, or $240/year (20% cheaper). 8 connections, 5,000 MCP calls/month, 3 team members.
- **Pro** — $75/month, or $720/year (20% cheaper). 20 connections, 25,000 MCP calls/month, 10 team members.
- **Agency** — $200/month, or $1,920/year (20% cheaper). Unlimited connections, 150,000 MCP calls/month, 25 team members.

Payments are processed by Stripe, monthly or annual, with annual paid upfront
for twelve months. Cancelling keeps the plan active until the end of the paid
period and then downgrades to Free. Your connections are never deleted or
disabled — you simply cannot add new ones beyond the Free limit. Exceeding the
monthly call limit returns a rate-limit error on further MCP calls, leaving data
and connections untouched.

There is no free trial. The Free plan is permanent and needs no card, and
first-time Starter, Pro and Agency subscribers have 7 days from their initial
payment to request a full refund. That window does not apply to upgrades,
downgrades or renewals.

- [Pricing](https://servemcp.com/pricing): current plans and the full comparison.
- [Refund & Cancellation Policy](https://servemcp.com/refund): the 7-day window and how to cancel.

## Company

- [Home](https://servemcp.com/): product overview.
- [Contact](https://servemcp.com/contact): support and sales enquiries.
- [Terms of Service](https://servemcp.com/terms)
- [Privacy Policy](https://servemcp.com/privacy)