# Unlimited MCP Tools: Break the 40 tools limit!

**URL:** <https://forum.cursor.com/t/unlimited-mcp-tools-break-the-40-tools-limit/78040>\
**Category:** Built for Cursor\
**Created:** [April 11, 2025, 2:24pm UTC](https://forum.cursor.com/t/unlimited-mcp-tools-break-the-40-tools-limit/78040 "2025-04-11T14:24:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![warpdev](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/warpdev/32/46307_2.png) [@warpdev](https://forum.cursor.com/u/warpdev)\
**Post date:** [April 11, 2025, 2:24pm UTC](https://forum.cursor.com/t/unlimited-mcp-tools-break-the-40-tools-limit/78040/1 "2025-04-11T14:24:54Z")

</div>

Hi guys, I’ve created an MCP server hub named `mcp-hub-mcp` to use Cursor without the 40-tool limit.

This hub connects to all servers defined in your `mcp.json` file and provides access through just two tools to minimize quota usage:

- `list-all-tools` : Lists all available tools from connected servers.
- `call-tool` : Executes a specific tool.

You can include only your frequently used tools in your primary config and delegate the rest to the hub.

### Setup Instructions

In your `.cursor/mcp.json` , configure the hub as follows:

```auto
{
	"mcpServers": {
		// ...other MCP servers,

		"mcp-hub": {
			"command": "npx",
			"args": [
				"mcp-hub-mcp",
				"--config-file",
				"~/.cursor/mcp-hub.json"
			]
		}
	}
}

```

Then, in `.cursor/mcp-hub.json` , list your desired MCP servers:

```auto
{
	"mcpServers": {
		// ...numerous MCP servers
	}
}

```

For optimal usage, consider adding the following guideline to your rule configuration:

```auto
If you can't find an appropriate tool, you can use the `list-all-tools` command to find it. You can execute the tool using the `call-tool` command.

```

I built this in just a few hours with Cursor, so I’d appreciate any suggestions for improvement. Thank you!

[[GitHub](https://github.com/warpdev/mcp-hub-mcp)] | [[NPM](https://www.npmjs.com/package/mcp-hub-mcp)]

---

<div class="post-metadata">

**Author:** ![rkaplan](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@rkaplan](https://forum.cursor.com/u/rkaplan)\
**Post date:** [April 15, 2025, 2:42am UTC](https://forum.cursor.com/t/unlimited-mcp-tools-break-the-40-tools-limit/78040/4 "2025-04-15T02:42:33Z")

</div>

Great idea - thanks

---

<div class="post-metadata">

**Author:** ![yunussahin](https://avatars.discourse-cdn.com/v4/letter/y/dbc845/32.png) [@yunussahin](https://forum.cursor.com/u/yunussahin)\
**Post date:** [April 19, 2025, 12:44am UTC](https://forum.cursor.com/t/unlimited-mcp-tools-break-the-40-tools-limit/78040/5 "2025-04-19T00:44:21Z")

</div>

Thanks!

---

<div class="post-metadata">

**Author:** ![Henkey](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/henkey/32/2442_2.png) [@Henkey](https://forum.cursor.com/u/Henkey)\
**Post date:** [May 5, 2025, 11:12am UTC](https://forum.cursor.com/t/unlimited-mcp-tools-break-the-40-tools-limit/78040/6 "2025-05-05T11:12:41Z")

</div>

That’s a neat idea

I was just tackling the same limit but from a single-server angle (my [self-hosted Supabase](https://github.com/HenkDz/selfhosted-supabase-mcp) one has a ton of tools). I went with adding a --tools-config flag where you point it to a JSON file. That file just lists the specific tools you want to activate ({“enabledTools”: [“list\_tables”, “execute\_sql”, …]}).

So instead of the hub’s list/call pattern, the server just loads the tools listed in that config file directly for the AI to see. It’s a simpler whitelist for managing one big server’s tools. Different approach for a slightly different problem, but aiming for the same goal.

Nice work on the hub!

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:40am UTC](https://forum.cursor.com/t/unlimited-mcp-tools-break-the-40-tools-limit/78040/7 "2026-06-18T10:40:56Z")

</div>

Closed on June 18, 2026, 10:40am UTC


