MCP Server Proxy

Created By
amirilovica year ago
Overview

what is MCP Server Proxy?

MCP Server Proxy is a proxy server that connects to multiple MCP servers, providing a unified interface for accessing various tools.

how to use MCP Server Proxy?

To use MCP Server Proxy, install the project via npm, create configuration files for each profile, and start the server with the desired command-line options.

key features of MCP Server Proxy?

  • Connects to multiple MCP servers simultaneously
  • Supports multiple configuration profiles
  • Tool name prefixing with server names
  • Operates in stdio or SSE mode
  • Profile-based configuration management

use cases of MCP Server Proxy?

  1. Managing multiple server connections for development tools.
  2. Simplifying access to various MCP tools through a single interface.
  3. Facilitating real-time data streaming with SSE mode.

FAQ from MCP Server Proxy?

  • How do I install MCP Server Proxy?

You can install it using npm with the command npm install.

  • Can I run the server in different modes?

Yes! You can run it in either stdio or SSE mode by using the --mode option.

  • How do I create a configuration profile?

Create a JSON file named config.<profile>.json with the necessary server configurations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
amirilovic
Star
0
Language
TypeScript
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