MCP REST

Created By
ivanboringa year ago
Exposes a SSE MCP server as a rest endpoints for tools. Only for testing
Overview

what is MCP REST?

MCP REST is a REST API wrapper around the Model Context Protocol (MCP) client, designed for testing purposes. It allows users to interact with the MCP server without maintaining a constant connection.

how to use MCP REST?

To use MCP REST, install it globally using npm or run it with npx. You can connect to an SSE server by specifying the server URL and port as options.

key features of MCP REST?

  • Provides REST endpoints for interacting with the MCP server.
  • Supports connection to custom SSE servers.
  • Offers debugging options for troubleshooting.

use cases of MCP REST?

  1. Testing interactions with the MCP server without a persistent connection.
  2. Listing available tools and checking connection status via API endpoints.
  3. Calling specific tools with arguments through REST API requests.

FAQ from MCP REST?

  • Is MCP REST suitable for production use?

No, MCP REST is intended for testing purposes only and should not be used in a production environment.

  • How do I install MCP REST?

You can install it globally using npm install -g mcp-rest or use it with npx mcp-rest.

  • What are the available API endpoints?

The available endpoints include /status to check connection status and /tools to list all available tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ivanboring
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago