undefined

points

[-]

> The problem with MCP is the initial setup friction is far greater than users login in themselves and grabbing the information they need.

Can you tell me more about this? With just-in-time client registration (DCR or CIMD) it seems like the MCP registration would be pretty simple.

Is it the configuration of the MCP client to know about the MCP server that is the issue?

Does the website need to be able to advertise "here's the corresponding MCP server" so that the "claude hits website" step becomes "claude hits website, discovers MCP server"?

by SkyPuncher5 hours ago|

parent|

[-]

Yes, it’s the friction of setting up the MCP server in the first place. Especially, in environments where that is not straightforward or easy to do. When our users are looking for information, they don’t want to figure out how to setup the MCP.

I don’t think this is about advertising an MCP at all. All of this can be accomplished with plain old HTTP requests. I want to be able to tell users “tell your LLM do go to https://example.com/only-bots”.

There’s absolutely no need for an MCP, because the website will tell the LLM everything it needs to know, including other actions and endpoints available.

by mooreds5 hours ago|

parent|

[-]

Have you seen WebMCP[0]? Had a customer ask about this recently.

It seems like it might be something of what you are looking for, since it leverages HTML to tell agents about website functionality.

One issue I see with WebMCP is that agents basically free-ride on user identity and authentication, which is problematic in some scenarios.

0: https://developer.chrome.com/docs/ai/webmcp