From OpenAPI to MCP server: how every call moves through GetMCP

GetMCP sits between any MCP client and your existing REST API. It terminates the protocol, validates each tool call, applies your auth and forwards the request, turning JSON-RPC into HTTP and HTTP back into JSON-RPC on every call.

MCP 2026-07-28 protocol revision Streamable HTTP and SSE transport Per-tool request mapping

One install, three responsibilities

GetMCP terminates the MCP protocol on an endpoint you host, runs your tool config to translate calls into HTTP requests, and pipes responses back into the protocol, adding logging, rate limits and auth on the way through.

tools/call result HTTP JSON Any MCP client Claude, Cursor, ChatGPT GetMCP mcp.yoursite.com Your REST API api.yoursaas.com JSON-RPC 2.0 Streamable HTTP or SSE User credentials Protocol terminator Tool runtime Auth, limits, logs GET /v1/projects POST /v1/tasks DELETE /v1/records/:id Pastes one URL Validates, authorises, records Unchanged
Protocol MCP 2026-07-28. Transport Streamable HTTP or SSE. Translation configured per tool.

Protocol terminator

The MCP endpoint lives on your own server. GetMCP answers initialize, lists tools, prompts and resources, and accepts tool calls over Streamable HTTP or SSE.

Tool runtime

Your tool config says which HTTP request each tool makes. GetMCP maps the call's arguments onto path, query, headers and body, and dispatches it.

Auth, limits and logs

Your auth strategy, your per-client rate limit and your call log are applied on the way through, before and after the upstream request.

Trace one request, end to end

Here is exactly what happens between the moment a user types a prompt in Claude and the moment your API answers.

Trace req_01HW8K3M, POST /mcp/my-mcp-server/tools/call

+0 ms
Client to GetMCP

Claude posts JSON-RPC tools/call with name create_task and arguments. The auth header is forwarded as configured.

192 B
+1 ms
Validate

GetMCP looks up the tool spec, validates the arguments against its JSON Schema and rejects malformed input before any upstream call.

+3 ms
Authorise

The configured auth strategy (API key, bearer, basic or OAuth) is applied. OAuth tokens are refreshed automatically if expired.

+4 ms
Rate limit check

The per-client counter increments for this server. Exceeded? GetMCP returns 429 immediately and never touches upstream.

+5 ms
GetMCP to your API

Arguments are mapped onto the configured HTTP request, path params, query, headers and body, and dispatched.

512 B
+138 ms
Your API responds

The response is captured. A 5xx triggers the configured retry policy with exponential backoff and jitter.

2.4 KB
+141 ms
Transform and respond

Optional response transforms run (rename, redact, reshape). The result is wrapped as a JSON-RPC tools/call response.

2.4 KB
+142 ms
Log and record

The full request and response, timing, client identity and status are persisted to your analytics table. Filter, replay or export to JSON or CSV.

logs

Four steps to a live MCP server

No separate infrastructure. No DevOps tickets. Any PHP host you already pay for becomes your MCP runtime, including a WordPress site, if that is what you run.

  1. Install

    Install it on any PHP host

    Requires PHP 8.3+ and a database. Put it on a subdomain like mcp.yoursite.com, then open /admin. Already on WordPress? Install the plugin there instead.

    curl -fsSL get.getmcp.com | bash
    ✓ installed, open mcp.yoursite.com/admin
  2. Server

    Create a server

    Pick a path (/mcp/my-mcp-server) and set the auth strategy. Each server gets a unique URL; the per-client rate limit you configured globally applies here automatically.

    server  production
    path    /mcp/my-mcp-server
    auth    Bearer or OAuth 2.0
  3. Tools

    Add tools, prompts and resources

    Import from cURL, OpenAPI, Swagger or Postman, or pick a template. Edit anything in the visual editor.

    import  openapi.json
    + 24 tools generated
    + 3 prompts, 2 resources
  4. Connect

    Share the URL

    Paste your server URL into Claude Desktop, Cursor, Windsurf or any MCP client. Done.

    // claude_desktop_config.json
    "mysaas": {
      "url": "mcp.yoursite.com/mcp/my-mcp-server"
    }

Why we built it this way

Four decisions that shape every part of GetMCP, from where it runs to how it handles the next protocol revision.

Your data, your domain

GetMCP runs on infrastructure you already control. Tool calls flow from the client, to your server, to your API. We never see the traffic, never store the credentials, never proxy the data.

Config, not code

Every primitive, tool, prompt and resource, has a UI in the admin. Engineers can drop into JSON when they want; everyone else stays in the visual editor.

Identity end to end

The user identity flowing into the MCP client flows all the way to your API. The same permission boundaries you already enforce stay in place. No magic.

Protocol updates ship as product updates

The MCP spec moves fast. We track it so you do not have to. When a new revision lands, an update brings it forward and your existing tool definitions keep working.

From login to a live MCP server, today.

Install it, import your API, share one URL.

Teams already shipping MCP servers with it

Rated 5.0 out of 5 by customers Read more reviews

I really like GetMCP. It makes my work much easier, and the connection stays stable without constant reconnecting. Through one MCP connection, I can give my AI access to the services I choose and let it handle many useful tasks across my tools.

Hamza El

Picked up GetMCP to connect our internal tools, and the initial setup was surprisingly fast. Probably saved me hours of configuration work. Looking forward to expanding our usage and future features.