Bring the MCP servers you already configured
Paste a Claude Desktop, Cursor or VS Code JSON file, a Codex TOML file, YAML, a claude mcp add command or a URL. GetMCP lists the servers it finds and creates the ones you pick as remote servers behind your own sign-in. The same dialog converts a config between formats, with your secrets replaced.
Paste, preview, pick
On the Servers page, Import offers From config. Paste the file's contents, the command or the URL and click Preview. Every server in the file appears with its address and how it signs in upstream. Tick the ones you want and click Import; each becomes a remote server, exactly as if you had used Connect Remote MCP.
- A header in the file, such as an Authorization header, is saved under the server's Upstream tab, encrypted; it does not change who may connect
- Nothing is created until you click Import, and only what you ticked
- A URL on its own imports one https MCP endpoint as one remote server
What the preview tells you
A client config mixes servers a web server can reach with ones it cannot. The preview sorts them before you decide.
Remote servers
An https address GetMCP can proxy. These are the ones you tick. Their headers come along as the stored credential, and the address is checked the same way as in Connect Remote MCP when the server is created.
Local servers
Started with a command such as npx or uvx, or a path on disk. They run on a desktop, not on a web server, so GetMCP never starts them and the preview says so, suggesting a hosted https version instead. The rest of the file imports as usual.
Servers that sign in with OAuth
On WordPress they import as per-user OAuth remote servers, and each person connects their own account afterwards. The standalone app cannot proxy them yet and lists them as not supported.
The formats it reads
Paste whichever you have. GetMCP works out the format from the content.
| Source | What GetMCP reads | Where it usually lives |
|---|---|---|
| Claude Desktop | mcpServers objects in JSON, with url, headers, command and args | claude_desktop_config.json |
| Cursor | the same mcpServers shape | ~/.cursor/mcp.json |
| VS Code | servers objects in JSON | .vscode/mcp.json |
| Codex | [mcp_servers.name] tables in TOML | ~/.codex/config.toml |
| YAML | the same shape as the JSON files | wherever you keep it |
| claude mcp add | the command line Claude Code prints, including --transport http and --header | a terminal or a README |
| URL | one https:// MCP endpoint | a vendor's docs |
Convert a config without leaking a secret
The Convert format tab takes a config in any of the supported formats and writes it out for Claude Desktop, VS Code or Codex. Every secret in the input is replaced with a placeholder, so the result is safe to paste into a chat, a ticket or a README. Fill the placeholders in locally.
- Hand a colleague the VS Code version of your Claude Desktop file in one step
- Tokens, keys and passwords never appear in the output
- Files are read in your browser and sent to your own install only; nothing goes to getmcp.com
// In: Claude Desktop { "mcpServers": { "northwind": { "url": "https://mcp.northwind.example/mcp", "headers": { "Authorization": "Bearer nw_live_8f3a2c…" } } } } // Out: VS Code, secret replaced { "servers": { "northwind": { "type": "http", "url": "https://mcp.northwind.example/mcp", "headers": { "Authorization": "Bearer <YOUR_TOKEN>" } } } }
They start closed
An import can create several servers at once, so none of them opens a door by itself.
No way in until you add one
Imported servers are created with WordPress sign-in and an empty allowed-users list on WordPress, or API-key authentication with no key on the standalone app. Open each server's Authentication tab and add the people who may connect, or create a key.
Tools off until you switch them on
Each imported server lists its upstream tools on the Tools tab with a switch. Turn on the ones your clients should have; the rest stay hidden from them.
Your tokens stay on your install
A header in the file becomes the server's stored credential, encrypted, and is never returned by the API. The Convert format tab replaces it with a placeholder before anything leaves the dialog.
The same checks as a remote server
Each address must be https and resolve to a public host, and the connection is pinned to the addresses that passed the check, on every call.
Questions about the config import
Will it import my local servers?
No. A server started with a command runs as a process on a desktop, and GetMCP runs on a web server. The preview lists those entries as not importable and says why; the remote servers in the same file import normally.
What happens to the tokens in my file?
On import, a header becomes the remote server's stored credential, encrypted on your install. On convert, every secret is replaced with a placeholder such as a token marker, so the output can be shared.
Which plan do I need?
The import creates remote servers, which are on the Pro plan and above. The Convert format tab is a tool in the same dialog.
Does anything leave my install?
No. The file is read in your browser and sent to your own install, which creates the servers. Nothing goes to getmcp.com.
Can I import a server that signs in with OAuth?
On WordPress, yes: it becomes a per-user OAuth remote server, and each person connects their own account from the WordPress admin. The standalone app lists such servers as not supported for now.
See it in use
All use casesPlan your week from your calendar and your Notion tasks
Claude reads next week's meetings from Google Calendar and your open tasks from Notion, then suggests where the focused work fits and adds the time blocks for you.
EClear your inbox in one conversation
Connect your mailbox to your own MCP server and let Claude find the threads waiting on you, write the replies as drafts and unsubscribe you from the lists you never read.
DAsk your shop database questions in plain English
Connect a MySQL, MariaDB or PostgreSQL database and ask Claude for best sellers, customers who stopped ordering or stock running low. The connection starts read-only and stays that way unless you change it.
Your config, now a server with a sign-in.
Paste the file you already have, pick the servers, and give your people one place to sign in.