Skip to main content
No. GetMCP is designed to be entirely no-code. You configure servers, tools, authentication, and parameters through the visual admin interface. For advanced use cases, WordPress hooks and filters are available for developers.
Any REST API that accepts HTTP requests. This includes:
  • Public APIs (weather, currency, geocoding)
  • Third-party services (Stripe, GitHub, Notion, Slack, HubSpot, etc.)
  • Internal company APIs
  • Other WordPress sites via REST API
  • WooCommerce APIs
If an API accepts HTTP requests, GetMCP can connect to it.
HTTPS is strongly recommended for production use, especially when transmitting API credentials. Most AI clients (Claude Desktop, Cursor, etc.) require or prefer HTTPS connections. For local development, HTTP works fine.
Yes. You can create as many servers as you need from a single WordPress installation. Each server gets its own unique URL, authentication settings, rate limits, and set of tools. This lets you organize tools by domain, client, or permission level.
API credentials (API keys, tokens, OAuth secrets) are encrypted at rest using libsodium (sodium_crypto_secretbox), which is built into PHP 8.0+. Credentials are only decrypted in memory during tool execution and are never logged or exposed in responses.
By default, all plugin data (database tables, options, capabilities, cron jobs) is removed on uninstall. You can enable Keep Data on Uninstall in GetMCP > Settings to preserve data for re-installation.
Yes. When an AI client connects to your MCP server, it calls tools/list to discover all available tools, their descriptions, and their input schemas. The AI then decides which tools to call based on the user’s request.
The Model Context Protocol (MCP) is an open standard created by Anthropic and donated to the Linux Foundation. It defines how AI clients communicate with external tools and data sources using JSON-RPC 2.0 over HTTP. GetMCP implements the Streamable HTTP transport variant of the MCP spec.
If your upstream API returns paginated data, you can:
  1. Pass pagination parameters (page, offset, limit) as tool input parameters
  2. Let the AI handle pagination by calling the tool multiple times
  3. Build an aggregation layer using WordPress hooks to merge pages before returning
Yes. The WordPress REST API exposes WooCommerce data (products, orders, customers) and GetMCP can proxy those endpoints. You can also use WordPress Query resources to expose WooCommerce data directly without authentication.
  • Tools: Execute actions by calling external APIs (get data, create records, send messages)
  • Resources: Expose read-only content to the AI (documentation, configuration, database content)
  • Prompts: Provide reusable prompt templates the AI can retrieve and use
Update via Plugins > Installed Plugins in WordPress admin, or use WP-CLI:
wp plugin update getmcp
GetMCP includes a database migrator that automatically handles schema changes on update.
Yes. WordPress plugin capabilities, custom hooks, and the React frontend can be customized. The REST API namespace (getmcp/v1) and MCP endpoint path (/mcp/) can be filtered for white-label deployments.
The MCP protocol supports Server-Sent Events (SSE) for streaming. GetMCP implements the SSE endpoint as part of the Streamable HTTP transport. Full streaming tool responses are on the roadmap.