171–180 of 217 posts
I use MCP all the time at work as well from Claude code etc, it's convenient with uniformity of configuration and access inside the harness.
Like as a deployed component in our customer facing app stack? Not being used in that context that I'm aware of. I think there's a couple use cases being worked on though.
Are devs/engineers using MCPs to do their work? Yeah. Datadog MCP, Atlassian MCP, Gitlab MCP, backstage mcp, and we have our documentation behind an MCP. All used daily.
MCPs are diminishing in value a bit, because AI Agents are getting smarter about using API/CLIs. For example, I use gh cli via Claude instead of their MCP, because I already had cli setup, so no need to use MCP. MCPs can potentially have great value if they cross multiple sources and combine results. For example at work we use an in-house MCP for log/metrics search across five different (legacy) systems. It finds cor…
MCP doesn't expose service credentials to the AI.
Earlier quoted context omitted.
This. We also thought MCP was useless, but now the workflows by ChatGPT and Claude are so good; it's as good as installing an app from the App Store. We launched MCP for our SaaS and immediately found users using it. API and MCP all are just buzzwords for customers. What they care about is whether they can get tasks done in our SaaS using Claude or ChatGPT. If that happens, it's a success.
Do you not expose a standard REST api?
I say MCP is just lightweight layer on top of REST and as long as it works for end users I don’t see any reason not to adopt it.
MCPs are diminishing in value a bit, because AI Agents are getting smarter about using API/CLIs. For example, I use gh cli via Claude instead of their MCP, because I already had cli setup, so no need to use MCP. MCPs can potentially have great value if they cross multiple sources and combine results. For example at work we use an in-house MCP for log/metrics search across five different (legacy) systems. It finds cor…
Earlier quoted context omitted.
I see benchmarks a lot working on this, and I honestly think there’s too many things to cover in this comment but: - this article doesn’t enable tool search for starters where tokens start at near zero for MCP too - even with the above, talks of the raw token count don’t consider that for very long trajectories the prompt cache amortises much of this cost, and a feature of MCP is you can also customise the tools to a…
> - this article doesn’t enable tool search for starters where tokens start at near zero for MCP too Is that why I have to constantly remind Claude and ChatGPT that they do have access to a Github plugin that can access my account, instead of trying and failing to use the gh cli?
Expect more on this. We are looking at the problem.
cgarvis is the only one who’s right All the others are cringe ad bots and the gullible/liars plugging MCP I give this thread: 8/10 cringe
It's very fast: most queries finish in < 10ms. Agents are able to find things quickly and efficiently even with vague questions. The app does a few things to minimize token output, but there's a long tail of potential token reduction strategies that I haven't gotten to yet.
Earlier quoted context omitted.
MCP is not just a rest api its a layer on top
A layer than honestly doesn't do much, as I understand it. What does MCP as a protocol actually solve? Is it more than a bandwagon?