An MCP server every MCP client can connect to, built from any REST API.
If it speaks MCP, it works with GetMCP. If it speaks HTTP, GetMCP can turn it into a tool. That is most of the surface area by design: we do not maintain integration code for individual apps.
Connect from any MCP-compatible client
Anyone implementing the protocol can connect. You ship one URL, your users paste it once, and your tools show up in their AI of choice.
Hand it to Claude or Cursor in one click
Every server has a Quick Connect panel. It checks the things that would stop a client from connecting, then opens Claude or installs into Cursor with the server filled in. Step-by-step instructions cover Claude Desktop, Claude Code, Windsurf, VS Code and the OpenAI playground.
claude_desktop_config.json; tools surface in chat.mcpServers in its settings.json.mcp_servers in config.toml.Bring any REST API. Templates for the common ones.
Point GetMCP at any HTTP endpoint that returns JSON and you have a tool. The catalogue of curated templates grows every release, but you are never blocked waiting for one.
Templates are a head start, not a limit
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. Pick one from the gallery, connect your credentials, and edit any tool it created.
- Pre-wired with sensible tool selections
- Every generated tool is editable
- Fork and customise without losing updates
More templates ship every release. See the changelog.
Don't see your stack? Bring it anyway.
If your API speaks HTTP, GetMCP can wrap it. Templates are a head start, not a limit.