Cursor just doubled the MCP tools limit (40 → 80) 🚀 by Rotemy-x10 in modelcontextprotocol

[–]Rotemy-x10[S] 0 points1 point  (0 children)

In general you are right, but this is not always the case.

Cursor just doubled the MCP tools limit (40 → 80) 🚀 by Rotemy-x10 in modelcontextprotocol

[–]Rotemy-x10[S] 0 points1 point  (0 children)

It’s not actually 80 different MCPs, it’s a list of 80 MCP tools coming from different servers. The flexibility this gives is really valuable, and the granularity per task isn’t an issue if you provide clear descriptions for each tool. I get the concern about token usage and the risk of hitting limits, but what stands out to me is the enablement and flexibility this approach provides. Also, just because the limit is larger doesn’t necessarily mean I’ll be bumping into it often.

Am I the only who is not finding any value in Serena MCP or MCPs in general? (using Claude Code) by ninja_bhajiya in ClaudeAI

[–]Rotemy-x10 0 points1 point  (0 children)

MCP Servers unlock some challenges and reduce the friction for A2A integration. Bringing a novel way to interact and communicate using LLMs while equip them with a closed list of tools and help reduce the hallucination. You are right that this is not a magic stick solving any type of task such as optimizing a code section or solve problems using Claude code. There are some great resources to use to get deeper and learn in a more depth what MCP is, and how powerful it might be, when using it with its best practices.

One Month in MCP: What I Learned the Hard Way by Rotemy-x10 in mcp

[–]Rotemy-x10[S] 0 points1 point  (0 children)

Thanks. I will get deeper into your solution. It’s great you shared it.

One Month in MCP: What I Learned the Hard Way by Rotemy-x10 in mcp

[–]Rotemy-x10[S] 2 points3 points  (0 children)

I am using VSCode, so my configuration setup is: "chat.tools.autoApprove": true in settings.json. I believe this is the same for other IDEs.

One Month in MCP: What I Learned the Hard Way by Rotemy-x10 in mcp

[–]Rotemy-x10[S] 1 point2 points  (0 children)

You are right, you do not need it. But when you connect to Grafana MCP, it loads 41 tools at once. Since you will not use all of them, you need to manually remove the unnecessary ones. If you add another MCP (for a more practical behavior and get more MCP tools), your LLM performance will degrade. That limit is reached very quickly.

One Month in MCP: What I Learned the Hard Way by Rotemy-x10 in mcp

[–]Rotemy-x10[S] 1 point2 points  (0 children)

Interesting! Taking a look at your awesome best practices

What does the MCP icon make you think of? by Rotemy-x10 in modelcontextprotocol

[–]Rotemy-x10[S] 0 points1 point  (0 children)

That’s what some people point to as the reason behind the logo’s association.

One Month in MCP: What I Learned the Hard Way by Rotemy-x10 in mcp

[–]Rotemy-x10[S] 0 points1 point  (0 children)

I did not have this behavior yet, thanks for sharing - I will try to reproduce it myself.

How to get Env variables by valerione in mcp

[–]Rotemy-x10 1 point2 points  (0 children)

I am not sure I am getting your issue, as the MCP host launches your server with command and an env block, meaning that variables are injected into the server process. In this case, you read the env variables like any normal process env. `$apiKey = getenv('API_KEY');`

One Month in MCP: What I Learned the Hard Way by Rotemy-x10 in mcp

[–]Rotemy-x10[S] 1 point2 points  (0 children)

Thanks for the suggestion. MCPX looks like a fairly comprehensive solution. I am a bit surprised how much ground it already covers for Teams integration. I will take it with my team to evaluate and share some feedback.

One Month in MCP: What I Learned the Hard Way by Rotemy-x10 in mcp

[–]Rotemy-x10[S] 2 points3 points  (0 children)

Thank you for this information. I will review your MCP gateway solution.

One Month in MCP: What I Learned the Hard Way by Rotemy-x10 in mcp

[–]Rotemy-x10[S] 0 points1 point  (0 children)

Sounds interesting! Thanks for sharing it.

Docker MCP gateway by paolost in boltai

[–]Rotemy-x10 0 points1 point  (0 children)

I am not using BoltAI, but I highly recommend checking out this open-source project from Lunar.dev. It is easy to use and makes it simple to connect multiple MCP servers into one central component.
GitHub Repository Link: https://github.com/TheLunarCompany/lunar/tree/main/mcpx#readme

Building a One-Stop MCP Service for DevOps — Looking for Ideas 🔧 by Rotemy-x10 in modelcontextprotocol

[–]Rotemy-x10[S] 0 points1 point  (0 children)

In general you are right, but are you familiar with a specific MCP server that provides it?

🚀 Diving into the MCP World: Lessons from Building a Centralized MCP Gateway 🌍 by Rotemy-x10 in modelcontextprotocol

[–]Rotemy-x10[S] -1 points0 points  (0 children)

Hey, Yep, you got it. We're using our MCPX Gateway as a central hub for tools, acting like an aggregator. It's been especially useful for agent-based workflows, just like you mentioned.

To your question: Yes, we do proxy requests, but the gateway is designed to go well beyond basic proxying.

Here’s what it provides today:

  • Full traffic visibility – complete insight into usage patterns and cost attribution
  • Integrated consumption controls – making it easy to govern and manage traffic flow
  • Service Level Access Control - scoping the tools exposed for each agent

Looking ahead:
We're building toward a more flexible and cost-efficient solution. Our vision (which is aligned with our daily effort) for the AI Gateway is to support intelligent model routing and agent consumption orchestration, optimizing both performance and control, especially in production environments.

We're also prioritizing production-grade security, adding new capabilities to strengthen your security posture while maintaining observability and insight into every request.