Claude Desktop MCP Setup: Connect a Server via MCPifex

To connect an MCP server to Claude Desktop, add a remote custom connector in your Claude account, paste in your MCPifex gateway URL with your API key, and switch it on in a conversation. You don't edit claude_desktop_config.json for this. That file is only for local servers that run on your computer.

Add the connector

Your connector URL is the gateway address with your key at the end:

https://mcpifex.com/mcp/<YOUR_MCPX_KEY>

Replace the placeholder with your full key. Then:

1. Open Customize → Connectors in your Claude account. Select Add custom connector, using the plus button where shown.
2. On Team or Enterprise, an owner adds it instead: Organization settings → Connectors → Add → Custom. Choose Web if it asks for the type.
3. Give the connector a name and paste the URL above.
4. If the dialog asks about authentication, choose No sign-in. Leave OAuth credentials and request headers empty.
5. Add the connector. On a team, members then find it under Customize → Connectors and connect to it themselves.
6. In a Desktop conversation, open the plus menu, choose Connectors and turn it on.

Anthropic's remote connector reference describes both the older single-screen form and a newer two-step form. Follow whichever your account shows. The URL is the same either way.

"No sign-in" doesn't make the endpoint public. Claude simply skips its own OAuth step, and MCPifex still checks the key in the URL.

Get the key first

You need an MCPifex instance and an API key before the steps above. The quickstart walks through it: create an instance, save the server's settings, pick the tools you want on, run Test connection, then generate a key.

A good first instance is PostgreSQL. Its write tool is off by default, so a read-only first test is safe. Never paste a database password into the URL. Only the MCPifex key goes there. The authentication reference explains what the key controls and how to revoke it.

Check that it works

Ask Claude for something specific and easy to verify, such as "List the schemas in my database." Look for the tool call in the conversation and check the data it returns. A confident answer with no tool call proves nothing.

The MCPifex portal logs every call per instance. If Claude says it failed, the log shows whether the request reached the gateway at all.

Why not the config file?

Anthropic separates remote connectors and desktop extensions. A remote connector talks to a server hosted elsewhere. A local extension runs software on your machine, for jobs like reading local files.

claude_desktop_config.json launches local processes with a command and arguments. An HTTP entry copied from another editor's config won't work there. The MCP project's local server tutorial covers that route. Your existing local servers keep working alongside the connector.

What your Claude plan allows

As of September 2026, Anthropic documents custom remote connectors on Free, Pro, Max, Team and Enterprise. Free accounts get one custom connector.

Remote requests come from Anthropic's cloud, even when you chat in Desktop. So a server that only your laptop can reach won't work as a connector. MCPifex's gateway is a public HTTPS address, so it does.

If it doesn't work

• No custom connector option: check your plan and role. On a team, an owner has to add the connector first.
• 401 error: the URL or key is wrong, or the key was revoked. Generate a new key and update the connector.
• Tools are missing: check which tools are enabled on the instance, and that the connector is switched on in this conversation. Disabled tools never reach Claude.
• The tool runs but errors: rerun Test connection in the portal and check access on the source system, such as the database.
• Protocol mismatch: MCPifex's gateway uses the handshake-based MCP transport. Clients on the current revision interoperate through the spec's backward-compatibility rules.

If a key leaks, revoke it in the portal and swap the URL in the connector. New calls stop within about a minute, and an open session is cut off on its next tool call.

About MCPifex

MCPifex runs MCP servers for you, so there's nothing to install. You pick a server in the marketplace, choose its tools and connect with one key. For a terminal setup with a bearer header, see Add an MCP server to Claude Code.