GetMCP gives you a complete Model Context Protocol surface — tools, prompts, resources, four kinds of auth, real-time analytics, rate limits, and an inspector — built into one plugin for WordPress. You map endpoints; we ship the protocol.
GetMCP exposes the three core MCP primitives through a visual editor. Every primitive is inspectable, versioned, and switchable per-server.
Each tool maps to a single HTTP request. Define inputs with full JSON Schema; outputs are typed and validated; per-tool scopes and rate limits are enforced before the request leaves your server.
Pre-author parameterized templates that surface as slash-commands inside Claude, Cursor, and Windsurf. Bundle the right tools and the right framing, so users get the right answer first try.
Expose docs, records, files, and live data as URI-addressable resources. The model fetches them on demand; you control what's discoverable, what's cached, and what's gated.
Run as many MCP servers as you need from a single WordPress install. Different products, different customers, different environments — each gets its own URL, auth, and analytics.
Four import paths in, one clean tool spec out. Or hand-author a tool when you need something bespoke. Every imported tool is editable — nothing is locked in.
Paste any cURL request copied from your terminal, browser devtools, or API docs. GetMCP parses the method, URL, query string, headers, and body — and generates a tool with a typed argument schema in seconds.
Upload an OpenAPI document — JSON or YAML — and GetMCP turns every operation into a tool, mapping schemas, descriptions, examples, and security requirements. Filter what to include before you commit.
Older Swagger 2.0 specs are first-class. GetMCP normalizes them into the same internal model as OpenAPI 3.x — you don't have to migrate the spec to use it.
Import full Postman collections, including environments and variables. Auth, headers, and pre-request scripts are translated into tool config; folders become tool groups.
For endpoints you'd rather not expose 1:1, build a tool in the visual editor. Pick the verb, paste the URL template, define each argument, and wire it to a downstream HTTP request — zero code.
Start from a curated template — Stripe, GitHub, Notion, Slack, WooCommerce, and more — pre-wired with sensible tool selections, so you can ship a useful server in minutes, not hours.
GetMCP supports the four auth patterns real APIs use — and forwards credentials end-to-end so your existing permission model stays intact. We don't proxy your secrets through our servers; nothing leaves your WordPress.
The simplest case — a single key, attached to every outbound request. Configure the header name (e.g. X-Api-Key) or the query parameter, then GetMCP injects it on every tool call.
Drop a static bearer for service-to-service tools, or pass tokens through from the MCP client header so each user calls your API as themselves.
For legacy systems and intranet APIs that still rely on HTTP Basic. Credentials are stored encrypted in WordPress and never round-trip through the AI client.
Full client-credentials and authorization-code flows, with automatic refresh. Configure the auth URL, token URL, scopes, and client credentials; GetMCP keeps tokens fresh.
Every tool call is logged with timing, payload size, response status, and the client that made it. Filter, replay, and export — without leaving WordPress.
Watch tool calls land as they happen. Drill into any call to see the request body, the upstream response, and the timing for every hop.
See which calls came from Claude Desktop, ChatGPT, Cursor, Windsurf, or anything else. Spot abuse, prioritize support, and decide what to optimize.
P50 / P95 latency, error rates, and call counts at the tool level. Catch a regressing endpoint before users do.
Filter logs by date, server, tool, client, or status — then export the result as JSON or CSV. Your data stays portable, no lock-in.
Rate limits, retries, an inspector, and templates — the operational tooling you'd otherwise build yourself.
Set a per-client rate limit once, and GetMCP applies it independently to every server you run. A client hitting 60 requests/min on Server A still has its own 60 requests/min on Server B. GetMCP retries 5xx responses with exponential backoff before failing the call — so a flaky upstream doesn't break the agent flow.
The Inspector is a built-in playground that calls your MCP server exactly the way Claude or Cursor will. Run any tool with real inputs, see the raw response, and replay calls from production logs with one click.
Start from a template instead of a blank server. Each template ships with a curated set of tools — the ones that are actually useful — so you skip the "which 80 endpoints do I expose?" question entirely.
GetMCP is a full implementation of the Model Context Protocol — not a subset. When the spec moves, a plugin update brings it forward. Your tools keep working.
Every method the MCP spec defines — initialize, tools/list, tools/call, prompts/get, resources/read — is implemented and conformance-tested.
Negotiated automatically per client. Long-running tool calls stream incremental progress; one-shot calls use plain HTTP.
Deprecate tools, add fields, or change schemas without breaking existing clients. GetMCP supports protocol negotiation and side-by-side tool versions.
When MCP ships a new revision, we ship a plugin update. Your existing tool definitions keep working — you don't migrate, the plugin does.