Show HN: Ismcpdead.com – Live dashboard tracking MCP adoption and sentiment

Post by bizzletk » Fri, Apr 03, 2026, 10:39 PM UTC

Imustaskforhelp wrote: post #6

paulirwin wrote: post #3

One thing that MCP solves well, that neither CLI apps (like the `gh` CLI for example) nor letting your LLM call arbitrary APIs via CURL does, is setting granular permissions per tool. Most agent frontends I've used like Claude Code only give you one level deep of CLI commands to authorize, which works fine for allowing commands like `docker build:*`. But for complex CLIs like GitHub, Azure, etc. it just doesn't scale…

can something of a cli utility be made which can deny any request from moving on, let's name this cli b which takes a user level configuration at say ~/.config or have a way to enter it via cli too or within the context of the folder which it is running in then we can have "b az vm delete test123" be run via these agents but then b checks if az vm delete command itself is allowed or not, and if it finds that its deni…

Post by kylecazar » Fri, Apr 03, 2026, 10:53 PM UTC

Post by dwb » Fri, Apr 03, 2026, 10:54 PM UTC

jameslk wrote: post #4

I don't think MCP is going anywhere, as much as I prefer CLIs or skills generally. Where MCP really shines is reducing friction and footguns for using a service, but at the expense of less versatility and expressiveness. You get a cookie-cutter way of using tools to interact with that service, which is easy to set up, doesn't require the user to download a CLI or have their agent interact with an API For power users…

Post by corlinp » Fri, Apr 03, 2026, 11:16 PM UTC

dfcowell wrote: post #13

paulirwin wrote: post #3

One thing that MCP solves well, that neither CLI apps (like the `gh` CLI for example) nor letting your LLM call arbitrary APIs via CURL does, is setting granular permissions per tool. Most agent frontends I've used like Claude Code only give you one level deep of CLI commands to authorize, which works fine for allowing commands like `docker build:*`. But for complex CLIs like GitHub, Azure, etc. it just doesn't scale…

This is solved by the agent having its own identity and credentials. Why would you share your login and identity with your AI agent? Access control and permissions should be handled on the backend by enforcing IAM on well-defined principals, not with MCP middleware. Claude can already bypass MCP and call APIs or use CLIs if it runs into blockers using MCP, so it’s not an effective point to implement the control.

Post by dnautics » Fri, Apr 03, 2026, 11:45 PM UTC

_andrei_ wrote: post #7

What's the purpose of this? There is no replacement for MCP. We need a protocol for calling tools that works with structured outputs, this is what we have.