Well it sure took "FastMCP" long enough. And the announcement lands at a time when its looking increasingly like CLI is the preferred method vs MCP. I'm sure in a few months time, even that will be out of date

▲

speedgoose 4 hours ago | parent [-]

MCP is superior to CLI by design, and it’s not even close. I don’t understand the sudden hype towards CLI for agents.

▲

zingar 4 hours ago | parent [-]

Would you mind elaborating on the superiority you perceive?

▲

TheMrZZ 4 hours ago | parent | next [-]

For MCP servers, there's no need to install a potentially untrusted software on your computer. Remote MCP can do very little harm, a CLI though? You're vulnerable to bad actors or supply chain attacks.

For client side MCP it's a different story.

▲

needs 4 hours ago | parent | prev | next [-]

Explorable by design, can be served through HTTP, OAuth integration.

▲

speedgoose 4 hours ago | parent | prev [-]

It has a json schema, that’s the main point. It also enforces good documentation by design. No need to get a man page or run the help command, it’s in the context. It can work remotely with authentication.

▲

ramon156 4 hours ago | parent [-]

Most CLI tools have JSON support. Your arguments fall flat pretty short.

I think MCP is fine in an env where you have no access to tools, but you cannot ripgrep your way through an MCP (unless you make an MCP that calls ripgrep on e.g. a repo, which in that case what are you doing).

	▲	vova_hn2 4 hours ago \| parent [-]
		Tool calls can have JSON schema enforced on lower level (token sampling). Although, I'm not sure if major providers do it, but I don't see any reason why they wouldn't.