Add one mcpifex entry to .cursor/mcp.json for a single project, or ~/.cursor/mcp.json for every project. Set the URL to https://mcp.mcpifex.com/mcp and your API key in an Authorization Bearer header. Reload Cursor and the server shows under Settings, MCP.

Start free The Free plan has 3 instances and needs no card.

Step by step

  1. Get a key. In the portal, create an instance, choose which tools are allowed, run Test connection and generate an API key (it starts with mcpx_).
  2. Pick the file. Use .cursor/mcp.json inside a project to share it with that project, or ~/.cursor/mcp.json to have it in every project. Create the file if it does not exist.
  3. Add one entry. Merge the mcpifex entry below into the mcpServers object. Keep any servers already there.
  4. Reload Cursor. Reload the editor. The server appears under Settings, MCP, with its tool count once it connects.
  5. Approve the first call. The first time the agent calls a tool, approve it in Cursor's prompt.
{
  "mcpServers": {
    "mcpifex": {
      "url": "https://mcp.mcpifex.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCPX_KEY>"
      }
    }
  }
}

Replace <YOUR_MCPX_KEY> with your key from the portal.

Which key form should I use in Cursor?

Cursor can send headers, so use the header form: the plain gateway URL plus Authorization: Bearer <YOUR_MCPX_KEY>. The key stays out of the URL.

Do not commit a project .cursor/mcp.json that holds a real key. Keep the key in ~/.cursor/mcp.json, or add the file to .gitignore.

What should I try first?

Cursor's agent works well with the database and App Store servers. Start with reads.

  • Using PostgreSQL, list the tables and explain how users relate to orders before I write a migration. (PostgreSQL server, query tool only.)
  • List my App Store Connect apps and show the latest review for each. (App Store Connect server, 38 write tools off by default.)
  • Check Google Search Console for pages with impressions but no clicks, then suggest title changes. (Google Search Console server.)

See every server on the marketplace, or read how the gateway controls which tools your AI can call.

Troubleshooting

  • The server shows red or zero tools. Check the JSON is valid, the header value starts with Bearer and a space, and the key is current. Then open the instance in the portal and confirm tools are allowed.
  • Cursor does not pick up my change. Reload the editor after editing mcp.json. If the same server name exists in both the project and home files, rename one so you know which entry is active.
  • The agent refuses to run a tool. Approve the call in Cursor's prompt. If the tool is a write tool, it is off by default: allow it on the instance in the portal first.

More errors and fixes are in the troubleshooting docs.

Full setup guides

Another client? See Connect your AI.

Ready to try it?

Run hosted MCP servers behind one endpoint and choose exactly which tools your AI can use.

Start freeBrowse the marketplace