Any remote MCP server, behind your own sign-in
Some of the tools you want already live on another MCP server: a vendor's hosted endpoint, a server a colleague runs, a service that only ships as MCP. GetMCP connects to it for you. Your people connect to GetMCP as usual, and your authentication, rate limits, PII redaction and call log sit in front of someone else's tools.
Connect it in one dialog
On the Servers page, Connect Remote MCP asks for a name and the remote server's Streamable HTTP address, and creates the server. Its Upstream tab is where you choose how GetMCP signs in to the remote server and test the connection: GetMCP opens an MCP session, reads the tool list and shows it.
- The address has to be https and resolve to a public host
- Choose None, a fixed header, Basic, or per-user OAuth on WordPress, and add extra headers such as an account id if the upstream wants them
- The new server starts closed, with WordPress sign-in and an empty allowed-users list, or API-key authentication with no key yet, until you let people in
What the client sees, and what it never sees
The client is given one address on your install and signs in to you. The remote server's own credential is stored once, encrypted, and used only by your server when it calls upstream. Nothing a client sends is forwarded.
- Rate limits, allowed IPs, PII redaction and the call log apply to remote tools exactly as to your own
- Bearer and Basic passthrough are not offered on a remote server: GetMCP never forwards a client's credential to someone else's server
- Calls are logged with the tool name and a Remote badge, and an error names the host, never the full address or the credential
// What your people put in Claude, Cursor or ChatGPT { "url": "https://mcp.yourapp.com/mcp/northwind-crm" } // What stays on your install, encrypted upstream https://mcp.northwind.example/mcp sign-in Fixed header header Authorization: Bearer •••••••••••• // What a client's own credential does upstream forwarded never
Four ways GetMCP signs in to the remote server
This is the upstream side: how your install proves itself to the other server. Who may connect to GetMCP for it is a separate setting on the server's Authentication tab, as for any server.
None
The remote server is open. Your own sign-in still protects it on the way in, and your rate limits still apply.
Fixed header
The remote server gave you a key or token. Pick the header name, paste the value, and it is stored encrypted and sent on every call. Extra headers every caller shares, such as an account id, are stored the same way.
Basic
A username and password, stored encrypted on your install and never returned by the API.
Per-user OAuth, on WordPress
The remote server signs each person in with OAuth. Give GetMCP its authorization and token endpoints and the client you registered there. Each person then connects their own account from Users and My MCP connections in the WordPress admin, and GetMCP uses their token only for their calls.
You choose the tools, and new ones wait for you
Every upstream tool is listed on the server's Upstream tools tab with its description and a switch. Turn on the ones your clients should have and save. The refresh button fetches the current list from the remote server, and tools it adds later arrive switched off with a New badge, so a vendor cannot put a new tool in front of your clients without you noticing.
- Switch a tool off and clients stop seeing it on their next tool list
- Descriptions and read-only hints come from the remote server, so clients see what its author wrote
- A remote server is never part of the MCP Gateway or a project gateway; clients connect to it directly
Checked before every connection
A server that opens connections to addresses you typed in needs limits that hold when a DNS answer changes or a vendor changes their mind. These are enforced on your install, before a request goes out.
Public addresses only
The address must be https and resolve to a public host. Localhost and LAN addresses are refused here even when Private Network Access is on for your own tools.
Pinned to the address that passed
GetMCP checks where the host resolves before every connection and pins the connection to the addresses it checked, so a DNS answer that changes a moment later cannot send the connection into a private network.
Your credential, not theirs
A GetMCP-managed key or OAuth token is never forwarded upstream, and a client's own credential never leaves your install. The remote server only ever sees the credential you stored for it.
Nothing on by itself
A new remote server has no way in until you add people or create a key, and its tools stay off until you switch them on. The same is true of servers created by the config import.
Logged like your own
Every call is logged with the tool name and a Remote badge, counted against the server's rate limit and your plan's call quota, and redacted for PII like any other call.
Errors name the host
When the remote server fails, the error your client sees names the host GetMCP was talking to, never the full address or the credential it used.
Questions about remote MCP servers
Can I connect a local MCP server, the kind started with npx?
No. Those run as a process on a desktop, and GetMCP runs on a web server that connects over https. The config import lists such servers as not importable and says why; the remote servers in the same file import fine.
Does the remote server see who my people are?
It sees your install's credential: the fixed header or Basic login you stored, or, with per-user OAuth, the token each person connected themselves. Your clients' identities and credentials stay on your install.
What happens when the vendor adds a tool?
Nothing, until you decide. Refresh on the Tools tab fetches the current list, and a tool that was not there before arrives switched off. Turn it on when you have read what it does.
Can I put a remote server in a gateway?
No. Remote servers are never part of the MCP Gateway or a project gateway. Clients connect to a remote server on its own address, with the sign-in you set for it.
Which plan do I need?
Remote servers are on the Pro plan and above, on both the WordPress plugin and the standalone app. Per-user OAuth upstream is a WordPress feature.
See it in use
All use casesKeep your SuiteDash clients and projects up to date from Claude
Look clients up by email, add new leads and move projects along in SuiteDash by asking Claude, through the Secure API your SuiteDash account already has.
KRun every client project in Kitchen.co from Claude
Connect the Kitchen.co API to your own MCP server once. Then ask Claude what's overdue across every client board, who you're waiting on, and have it post the update in the right conversation.
SMake social images from your Switchboard Canvas templates by asking Claude
Write the headline in the chat and get finished images back in every size you need, rendered from your own Switchboard Canvas templates.
Someone else's tools, your rules.
Connect the remote server once, pick the tools, and let your people sign in to you.