WebMCP

Summary

WebMCP A proposal and code for websites to support client side LLMs WebMCP allows websites to share tools, resources, prompts, etc. to LLMs. In other words, WebMCP allows a website to be an MCP server. No sharing API Keys. Use any model you want. Here's a simple website I built that is WebMCP-enabled It comes in the form of a widget that a website owner can put on their site and expose tools to give client-side LLMs what they need to provide a great UX for the user or agent. The look, feel, how it's used, and security are all absolutely open for contribution / constructive criticism. MCP Clients directly building WebMCP functionality seems like an ideal outcome. An end-user can connect to any number of websites at a time - and tools are "scoped" (by name) based on the domain to simplify organization. Super Quick Demo (20 seconds, Sound on 🔊) webmcp.mp4 Getting started (using your LLM with websites using WebMCP) Installation Just specify your MCP client ( claude , cursor , cline , windsurf , or a path to json) npx -y @jason.today/webmcp@latest --config claude If you're interested in setting it up manually, use the command npx -y @jason.today/webmcp@latest --mcp . Auto-install was inspired by Smithery, but their code is AGPL so I wrote this myself. If it doesn't work for you or you don't see your mcp client, please file an issue. Using WebMCP When you're ready to connect to a website, you can ask your model to generate you an mcp token. Copy the token and paste it to the website's input. As soon as the website registers with it, it's thrown away and cannot be used for subsequent registrations or anything else. The website will receive its own session token for making requests. If you'd rather your model / service never see the token, you can manually execute npx @jason.today/webmcp --new instead. Some MCP clients, including Claude Desktop, need to be restarted to get access to new tools. (at least at time of writing) To disconnect, you can close the browser tab, click...