mcp-server-proxy

Created By
leizongmina year ago
Converts MCP protocol's SSE transport layer to a standard HTTP request/response.
Overview

What is mcp-server-proxy?

The mcp-server-proxy is a tool that converts the MCP protocol's SSE transport layer into a standard HTTP request/response, simplifying the development and usage of MCP Servers.

How to use mcp-server-proxy?

To use mcp-server-proxy, install it via Go, and then use the provided commands to inspect requests or serve as a proxy between MCP Clients and standard HTTP endpoints.

Key features of mcp-server-proxy?

  • Converts MCP protocol's SSE transport to standard HTTP requests/responses.
  • Provides request and response inspection functionality for studying MCP Client and Server interactions.
  • Supports methods like initialize, tools/list, and tools/call.

Use cases of mcp-server-proxy?

  1. Simplifying the integration of MCP Clients with existing HTTP services.
  2. Facilitating the development of applications that utilize the MCP protocol without needing to handle SSE details.
  3. Debugging and inspecting the interactions between MCP Clients and Servers.

FAQ from mcp-server-proxy?

  • Is mcp-server-proxy easy to set up?

Yes! It requires minimal configuration, just set the service address to get started.

  • What programming languages can I use with mcp-server-proxy?

You can use any programming language that can make HTTP requests, as it standardizes the communication.

  • Can I contribute to mcp-server-proxy?

Absolutely! Contributions and pull requests are welcome.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
leizongmin
Star
-
Language
-
License
-

Recommend Servers

View All
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