[dead]
MCP Hello Page
41–50 of 58 posts
Re: MCP Hello Page
#42First time I access this website, as far as I know (via a corporate VPN, and the first time I see this kind of blocking from Cloudflare while using that VPN):
"Sorry, you have been blocked
You are unable to access hybridlogic.co.uk
Why have I been blocked?
This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data."
Re: MCP Hello Page
#43MCP = Model Context Protocol, an interface for LLMs to retrieve information and perform actions
Re: MCP Hello Page
#44First time I access this website, as far as I know (via a corporate VPN, and the first time I see this kind of blocking from Cloudflare while using that VPN): "Sorry, you have been blocked You are unable to access hybridlogic.co.uk Why have I been blocked? This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several ac…
Same, I don't use any VPNs though.
Re: MCP Hello Page
#45I have spent ~3 months working on various aspects of an MCP server builder at my day job and I hadn’t considered this solution to the nightmare of getting non technical end users connected. I shall be borrowing it next week!
Re: MCP Hello Page
#46Sorry, you have been blocked.
Webmaster, maybe check your firewall? :/
Re: MCP Hello Page
#47Excellent. Tiny affordances like this should be more commonplace, IMO. I think this probably also helps when truly clueless users drop the link into an agent directly, because then the agent will relay the message to the user.
i have experimented with this idea a bit
i have learned that if the request accepts html, just give them that, however, some agents will ask for text/markdown, so just give them that.
you can even take OPs ideas further: text/html? serve html help page; text/markdown? serve the same but pure text, maybe nudge the agent on how to install the mcp; application/json? pass through to the mcp app.
the whole llms.txt thing could have been that
Re: MCP Hello Page
#48Haven’t people caught on lately that MCP is a dead end and that we’re better off feeding shell scripts to agents with some brief documentation?
Re: MCP Hello Page
#49I never quite understand why /mcp endpoint is needed. You can still keep using Rest API with swagger docs and tell the AI to read the swagger docs. It's the same thing. The entire Rest API specification is a lot more flexible than the JSON RPC format /mcp uses.
rest api with swagger docs requires one extra hop to pull the details necessary to interact with the api, and it pollutes context in a similar way as mcp.
ideally what you would have is skills + scripts that the agent can load progressively to interact with the api
or even better: a single cli tool the agent is aware of, and which combines `--help` output with `tldr` tips, when the command is incomplete, and prints out helpful error messages when the incantation is wrong
Re: MCP Hello Page
#50Haven’t people caught on lately that MCP is a dead end and that we’re better off feeding shell scripts to agents with some brief documentation?
folks have caught on to it, but from a service provider perspective it's not as easy to deliver the solution
mcp is basically `claude mcp add `
skills require multi step marketplace registration, refresh, then picking the right skill out of *checks notes* 116 skills on the official marketplace + however many skill come with the new marketplace
cli tools may be a bit better, maybe they're there already because you need them to interact with deployment, or they might be a simple `brew add `