---
title: "Add Every MCP Server to Cursor at Once — onemcp"
description: "Give Cursor's agent all your MCP tools through one endpoint in ~/.cursor/mcp.json. Add servers once, keep credentials host-side, and cut context bloat."
url: "https://onemcp.dev/use-cases/cursor/"
---

# All your MCP tools in Cursor, from one endpoint.

Instead of a growing wall of servers in ~/.cursor/mcp.json, add a single onemcp portal. Cursor's agent gets every tool you've curated — with none of the per-request token overhead.

## Connect Cursor in three steps

1. **Curate a portal** — Add the MCP servers you want into a onemcp portal and authenticate them once.
2. **One mcp.json entry** — Drop your portal URL into ~/.cursor/mcp.json — a single server instead of a dozen.
3. **Code and let it call** — Cursor's agent searches, describes, and executes your tools through Code Mode.

Add to ~/.cursor/mcp.json:

```
{
  "mcpServers": {
    "onemcp": {
      "url": "https://portal.onemcp.dev/mcp"
    }
  }
}
```

## Why point Cursor at onemcp

- **No more config sprawl** — Manage servers in the portal, not in every teammate's mcp.json.
- **Secrets never touch the repo** — Upstream OAuth and tokens stay in the portal, out of your project config.
- **Faster, cheaper prompts** — ~90% smaller tool overhead means Cursor keeps its context for your code.

## One line in mcp.json. Every tool in Cursor.

Create a portal, paste the URL into Cursor, and start building.