GetMCP

GetMCP turns any REST API into a production-grade, self-hosted MCP (Model Context Protocol) server from a WordPress plugin — zero protocol code — so your product becomes usable from Claude, ChatGPT, VS Code, and Cursor.

What is GetMCP?

GetMCP is a self-hosted WordPress plugin that converts any REST API into a Model Context Protocol server, the standard that lets AI agents like Claude and ChatGPT call external tools. Instead of hand-writing JSON-RPC transports, OAuth flows, and session handling against a spec that revises itself every few months, you install the plugin on a WordPress subdomain (mcp.yoursite.com), define one server namespace per product or tenant, and import tools from a pasted cURL command, an OpenAPI 3.0/3.1 or Swagger 2.0 file, or a Postman v2.1 collection — GetMCP generates typed tools, prompts, and resources with parameter validation. Users then connect from any MCP client (Claude Desktop, Claude Code, ChatGPT, VS Code, Cursor, Zed) by pasting one server URL, with credentials passed straight through and OAuth 2.1 (mandatory PKCE) or per-server API keys handled on your side. The admin dashboard shows server health, call volume, latency, and filterable logs with one-click replay, and a built-in playground lets you test each tool before it goes live. Because it runs entirely on your own WordPress install, call data and credentials never touch a third-party cloud — a deliberate contrast to hosted API-to-MCP converters. It's built by InfiWebs, the Pune-based team behind the long-running FlowMattic WordPress automation plugin, and launched on RocketHub in August 2026 at $49–$499 lifetime across five tiers mapped to the vendor's $99/yr Pro and $299/yr Agency plans, with a free forever Solo plan to trial first. It's impressively specced for a v1 (encrypted credential storage, PII redaction, JMESPath pruning, tamper-evident logs), but it has zero independent reviews, is WordPress-only with no standalone ETA, and its 'lifetime' rides on a protocol that's still being defined.

Key Features

• *No-Code MCP Server Builder** — Turn any REST API into a compliant MCP server from the WordPress admin with tools, prompts, and resources generated for you.
• *Four Import Methods** — Bring in a pasted cURL command, an OpenAPI 3.0/3.1 spec, a Swagger 2.0 file, or a Postman v2.1 collection and get typed tools with validation.
• *Any MCP Client** — One server URL works with Claude Desktop, Claude Code, ChatGPT, VS Code, Cursor, Zed, and any client implementing MCP over HTTP or SSE.
• *Self-Hosted & Private** — The plugin runs on your own WordPress site; credentials and call data never leave your server, with no per-call fees.
• *OAuth 2.1 & API Key Auth** — Mandatory PKCE (S256), rotating refresh tokens, and hashed per-server API keys for inbound client authentication.
• *Dashboard, Analytics & Logs** — Server health, call volume, latency, and status per tool, with filterable logs, JSON/CSV export, and one-click replay.
• *Built-in Playground** — Test every tool with real inputs and inspect exact responses before you expose it to users.
• *Per-Client Rate Limits & PII Redaction** — Control abuse with global per-client limits and scrub emails, cards, SSNs, phones, IPs, and custom patterns from logs and responses.
• *Prompt & Resource Support** — Ship pre-authored prompt templates (slash-command workflows) and read-only resources alongside your tools.

Who is it for?

• SaaS founders who want their product usable from Claude and ChatGPT without hiring an MCP engineer or spending weeks on protocol code
• WordPress and WooCommerce owners who want shoppers browsing catalogs, placing orders, and tracking shipments from within an AI assistant
• Agencies that want to resell branded MCP servers across 20–200 client sites as a new paid service
• No-code builders and automators who can paste a cURL command but won't touch JSON-RPC or OAuth
• Dev tools teams that want deploy, rollback, and log commands exposed to AI coding assistants with scoped auth
• Internal ops and IT leads wiring private APIs into a self-hosted team copilot behind their own firewall

Who is it NOT for?

• Developers comfortable hand-writing an MCP server — GetMCP's value is abstracting exactly what you already know how to do
• Teams that refuse to run WordPress — the standalone/Docker self-hosted version is promised but has no ETA
• Buyers who just want to consume existing MCP servers (GitHub, Notion, Stripe) — this builds servers, it doesn't catalog them
• Anyone who needs more than 200 licensed sites on a single license — the top tier is deliberately capped
• Risk-averse buyers who require a proven product with independent reviews — GetMCP has none yet