This exposes your MCP over rest so you can easily use it in your APIs without painful RPC

REST to MCP conversion rules:

1. Path params come from URL segments after method name
2. Required simple params (string/number/boolean) go in query params
3. Optional simple params go in query params
4. Complex objects/arrays go in request body
5. Special case for tools/call: POST body or GET query params become "arguments"

For example, a toolcall to tool add becomes /tools/call/add?a=1&b=1

Note: This focuses on a REST-suitable subset of MCP methods. Server to client methods or streaming methods like notifications are omitted.

Usage:

import { convertRestToMcp } from "rest-mcp";
export default {
  fetch: async (request) => {
    if (new URL(request.url).pathname === "/mcp") {
      return handleMcp(request);
    }
    // Handle rest over mcp
    const mcpRequest = await convertRestToMcp(request);
    if (mcpRequest) {
      return handleMcp(mcpRequest);
    }
    return new Response("Not found");
  },
};