Cursor's MCP tool limit was eating my context. Here's how I got around it.

I kept adding MCP servers to Cursor and hit the wall fast. Once you connect a handful, the tool definitions pile up, Cursor starts warning that you have too many tools enabled, and a big chunk of the context window is just tool schemas before you've typed anything.

I didn't want to keep manually enabling and disabling servers depending on what I was doing that day. So I ended up building a gateway that sits between Cursor and all the servers. Cursor only sees a couple of meta-tools (a search and a call), and the actual tool definitions load on demand when the model needs one. Everything stays connected, the upfront tool block drops to a few hundred tokens, and the "too many tools" warning goes away.

Disclosure, I made it. It's called Toolport and it's open source. Not trying to hard sell, mostly sharing because the tool-limit thing seems to trip up everyone who gets deep into MCP.

If you want to see the token difference for your own setup there's a calculator here, https://toolport.app/calculator

Happy to answer questions about how it works with Cursor specifically.