WebMCP

MCP built for the web!

WebMCP is brought to you by Svix!

🚀 What is WebMCP?

WebMCP is a simplified, web-native reimagining of MCP (Model-Command Protocol) designed to work seamlessly in modern web environments.

Traditional MCP was built with the assumption that the client is a desktop application, which introduces a number of problems when trying to run or consume MCP servers in the browser or over standard web APIs.

WebMCP fixes this by redefining MCP for the web:

• 🌐 Pure REST API interface
• ⚙️ Easy to implement — just like any other web API
• 🔒 No need to run arbitrary local MCP servers
• 🔄 Enables direct web/browser access to MCP-compatible functionality
• 🧩 Compatible with existing tools like Cursor via a reference WebMCP → MCP bridge

🧠 Why WebMCP?

While MCP has gained traction as a protocol for tooling like Cursor, its architecture wasn't designed with web-first principles in mind. It assumes:

• Clients are running on local machines
• Servers can run arbitrary code locally
• End users can install and maintain local infrastructure

This isn't scalable or friendly for:

• Hosted environments
• Web-based tools (e.g., ChatGPT, browser extensions)
• Non-technical users

Anthropic and others are trying to address this by bolting HTTP transport layers onto traditional MCP — but the core issues remain.

WebMCP takes a different approach: start with the web in mind.

🌐 How It Works

WebMCP defines a minimal set of RESTful APIs that MCP clients (like Cursor) can use to interact with your service.

Instead of building or running a full MCP server, you simply expose standard web endpoints. We've designed these to be as simple and familiar as possible to typical web developers.

Example Architecture:

Browser / Client
   ↓
 WebMCP API (your REST server)
   ↓
 Reference WebMCP → MCP Bridge (optional)
   ↓
  Cursor / MCP client

• You only need to implement the WebMCP API.
• The reference bridge server lets traditional MCP clients interface with WebMCP endpoints today.
• In the future, clients like Cursor could talk directly to WebMCP without any local server.

🛠️ Getting Started

1. Build a WebMCP-compatible API

Implement the core WebMCP REST endpoints as described in our API spec.

These are lightweight and should be easy to add to any existing web service.

2. (Optional) Run the WebMCP Reference Bridge

This open-source adapter translates WebMCP APIs into a traditional MCP server interface.

# Clone and run the reference bridge
git clone https://github.com/your-org/webmcp-bridge.git
cd webmcp-bridge
npm install
npm start -- --endpoint=https://your-webmcp-api.com

3. Use with Cursor or other MCP clients

Once running, the reference bridge can be used like any other MCP server.

🔍 Example Use Cases

• Host your own toolchains for Cursor without forcing users to run a local server
• Allow browser-based UIs (like ChatGPT or custom dev tools) to use MCP-based functionality
• Eliminate the devops burden of managing MCP servers for every user

📚 Documentation

• WebMCP API Specification
• MCP Overview
• Reference WebMCP Server
• Bridge MCP Server (WebMCP to MCP)

🧪 Status

WebMCP is still evolving, but it's usable today. We're actively working on:

• Finalizing the WebMCP API spec
• Tightening the bridge compatibility with MCP clients
• Gathering feedback from early adopters

🤝 Contributing

Please open an issue or pull request to discuss improvements.

📜 License

MIT