MCP REST

@ivanboring

About MCP REST

Exposes a SSE MCP server as a rest endpoints for tools. Only for testing

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-rest": {
      "command": "npx",
      "args": [
        "mcp-rest"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP REST?

MCP REST is a REST API wrapper around the Model Context Protocol (MCP) client. It allows you to interact with an MCP server over HTTP without maintaining a constant client connection. It is intended for testing purposes only, not for production use.

How to use MCP REST?

Install globally via npm install -g mcp-rest or run with npx mcp-rest. Start the server with options such as --type (SSE only), --url (SSE server URL), --port (Express port), and --debug. Once running, use the provided API endpoints: GET /status to check connection, GET /tools to list tools, and POST /tools/:toolId to call a specific tool with JSON arguments.

Key features of MCP REST

Wraps MCP client as a RESTful API.
Supports SSE (server-sent events) connection type.
Configurable Express server port and SSE URL.
Debug logging with --debug flag.
Simple HTTP endpoints for status, tools, and tool calls.

Use cases of MCP REST

Quickly test MCP tools without setting up a persistent client.
Integrate MCP functionality into HTTP-based workflows or scripts.
Explore available tools and their parameters via GET /tools.
Validate tool calls with custom arguments using POST /tools/:toolId.

FAQ from MCP REST

What is MCP REST meant for?

It is designed for testing and experimentation with MCP, not for production use. The README explicitly states it is "just for testing, not to use for real."

How do I install and run MCP REST?

Install globally via npm install -g mcp-rest or use npx mcp-rest directly. Run with optional arguments like --port 4000 or --debug. The default SSE URL is http://localhost:8000/sse.

What connection types does MCP REST support?

Currently only SSE (server-sent events) is supported, as indicated by the --type option defaulting to "sse".

How can I call a tool through the REST API?

Send a POST request to /tools/:toolId with a JSON body containing an "arguments" object. Example: curl -X POST http://localhost:3000/tools/exampleTool -H "Content-Type: application/json" -d '{"arguments": {"param1": "value1"}}'.

What should I do if I encounter connection issues?

Use the --debug flag to see detailed logs, check the /status endpoint to verify connection status, and ensure your MCP server/process is running and accessible.

Frequently asked questions

What is MCP REST meant for?

It is designed for testing and experimentation with MCP, not for production use. The README explicitly states it is "just for testing, not to use for real."

How do I install and run MCP REST?

Install globally via `npm install -g mcp-rest` or use `npx mcp-rest` directly. Run with optional arguments like `--port 4000` or `--debug`. The default SSE URL is `http://localhost:8000/sse`.

What connection types does MCP REST support?

Currently only SSE (server-sent events) is supported, as indicated by the `--type` option defaulting to `"sse"`.

How can I call a tool through the REST API?

Send a POST request to `/tools/:toolId` with a JSON body containing an `"arguments"` object. Example: `curl -X POST http://localhost:3000/tools/exampleTool -H "Content-Type: application/json" -d '{"arguments": {"param1": "value1"}}'`.

What should I do if I encounter connection issues?

Use the `--debug` flag to see detailed logs, check the `/status` endpoint to verify connection status, and ensure your MCP server/process is running and accessible.