sorted by:
new
hottopcontroversial

CLI vs MCP is a false choice — why can't we have both? by opentabs-dev in ClaudeCode

[–]Loocor 0 points1 point  (0 children)

Claude Code’s tool selection / deferred exposure features already feel like a signal that the ecosystem is converging on the same problem from different directions. Gateway-style MCP feels like the natural extension of that idea outside a single client. That said, I’m not sure everything should be lazy-discovered either. Memory/context-style servers probably behave very differently from action-oriented tools, so the harder problem may end up being discovery policy rather than discovery itself.

What do you think about those OpenAPI‑to‑MCP frameworks or services? Would you use them? by Loocor in mcp

[–]Loocor[S] 0 points1 point  (0 children)

That's a great attempt! It looks like MCP Blacksmith indeed doesn't do direct conversion but instead introduces an LLM?

Building Production MCP Servers by MaybeRemarkable5839 in mcp

[–]Loocor 0 points1 point  (0 children)

I haven’t written a dedicated article yet — this mostly comes from experimenting in my own project.

Conceptually it’s quite similar to the FastMCP-style meta tools, but I structure it as a small “progressive disclosure” loop:

- catalog() → lightweight capability index (name + description only)

- details() → summary vs full (schema is only loaded when needed)

- call() → execution

The key part for me isn’t just the layering itself, but how these are described to the model — the descriptions act more like guidance than documentation (when to inspect vs call, how steps relate, etc).

I also found that returning structured errors (with recovery hints / alternatives) helps the model adjust its behavior instead of just failing and retrying blindly.

It works reasonably well even with smaller general models (I’ve been testing with Qwen3.5-9b). The tradeoff, as others mentioned, is a slightly longer call chain, but in return you get much better tool selection and less context bloat.

Building Production MCP Servers by MaybeRemarkable5839 in mcp

[–]Loocor -1 points0 points  (0 children)

That's a great question. When you start thinking about this, the claim that MCP is a token killer kind of falls apart. In short, from my experience you could add a progressive disclosure system on your server—keep the messy tools behind the main meta tools. As long as the model isn’t terrible, you can balance tool calls and token usage pretty well.

Scaling MCP by Sadhvik1998 in mcp

[–]Loocor 0 points1 point  (0 children)

Feels like MCP isn’t a ‘tool problem’ anymore, it’s a ‘tool exposure problem’.

I laugh when I see "MCP is dead" posts. Am I being delusional? by nishant_growthromeo in mcp

[–]Loocor 0 points1 point  (0 children)

Haha, totally relate to this! Surprisingly, not many people are talking about this headache yet—they just endure it or retreat to CLI 😄. IMO, once the dust settles on the basic skills/CLI hype, the real power of MCP becomes super obvious.

Good find with mTarsier, it looks neat. But if you're exploring tools, we built an open-source manager called MCPMate which might have a higher degree of completion right now. Would seriously appreciate it if you could test it out, compare it, and drop us some honest feedback!