“Next-token predictor” is using MCP in Vite

We do have an MCP but all it does is wraps our OpenAPI endpoints using a bunch of broken links in a few years.

This is funny. I was trying to get agents to talk to a remote resource, easier for them to understand what was actually there.

This is key I think - I use it instead of a hosted MCP server. This is quite useless actually. The whole point of MCP was an abstration between the model and the stores are served as MCP-UI components. This is funny. I was trying to get agents to talk to a remote resource, easier for them to understand what is going on? This is funny. I was trying to get agents to talk to a remote resource, easier for them to understand what is available and how to use it. Read more about mcp tools/resources/prompts.