Project gateways, remote MCP servers, and the people you choose
- Project gateways: publish the tools of up to 50 servers under one endpoint, each tool named
server-slug__tool, behind the gateway’s own sign-in. Saving one with a weaker sign-in warns which member servers it hides - Remote MCP servers: proxy another MCP server’s tools through GetMCP behind your own client authentication, and switch each upstream tool on or off. Addresses are checked before every connection and pinned, so DNS cannot redirect them to a private address. On WordPress the upstream can also be per-user OAuth, where each person connects their own account
- Import a client config: paste a Claude Desktop, Cursor or VS Code JSON file, a Codex TOML file, YAML, a
claude mcp addcommand or a URL, preview the servers it lists and create the ones you pick as remote servers. Convert a config between the Claude, VS Code and Codex formats, with secrets replaced by placeholders - Client API keys on the Authentication tab: create a key per client, shown once with an optional expiry, see when each was last used and revoke it. A status line says whether the server accepts only your keys, forwards any key to your API, or refuses everyone
- WordPress Abilities as MCP tools (WordPress 6.9 and later): Import Tools → From WordPress Abilities turns any registered ability into a tool, run as the signed-in user or the server’s “Run abilities as” user. Abilities that are not read-only need a confirmation to import
- WordPress sign-in with an allowed-users list: pick the people who may connect to a server. An empty list lets nobody in, administrators included, and the list is checked on every request and at every OAuth step
- Standalone app: Users and My account. Add people by an emailed link or a password, make them admins or members, and let everyone reset a password by email. Members see their own account and, when allowed, Chats. Server logos and brand images come from the app’s own media library
- Activation codes for sites getmcp.com cannot reach, such as a local install: generate a code in your account, paste it on the License page, or set it in
.envorwp-config.php - Logs keep the tool name and the gateway a call came through, with a Remote badge for remote servers and a Via column in the CSV export
- Hardening: gateways no longer pass a caller’s credential to member servers, and a server that forwards a caller’s credential cannot also store one. OAuth codes are bound to their exact redirect URI and grants to the issuing server, per-user OAuth sign-ins to the browser that started them. The private-address guard sees through NAT64 and 6to4, pins every checked address, and bypasses proxies. A server with mailbox, database or file tools refuses every caller until you create a key, and mailbox folder names and read-only SQL are checked more strictly