MCP-Proxy

Created By
loocora year ago
MCP-Proxy 是一个 MCP(Model Context Protocol)代理服务器和客户端工具集的实现,旨在简化与 MCP 服务器的交互,并提供一种统一的方式来访问多个 MCP 服务器的代理演示项目
Overview

What is MCP-Proxy?

MCP-Proxy is an implementation of a Model Context Protocol (MCP) proxy server and client toolset designed to simplify interactions with MCP servers and provide a unified way to access multiple MCP servers.

How to use MCP-Proxy?

To use MCP-Proxy, you can run the proxy server using the command python mcp_proxy.py and manage MCP servers with the client tool mcp_client.py. You can also call specific tools using mcp_tool.py with appropriate arguments.

Key features of MCP-Proxy?

  • MCP proxy server that integrates multiple MCP server tools into a unified interface.
  • Client tools for managing and querying MCP servers.
  • Support for calling various tools provided by MCP servers.
  • Configuration management through JSON files.

Use cases of MCP-Proxy?

  1. Developing AI applications that require access to various external tools and resources.
  2. Integrating into IDEs like Cursor that need to access multiple MCP server tools.
  3. Automating workflows that require combining multiple tools.

FAQ from MCP-Proxy?

  • What is the purpose of MCP-Proxy?

MCP-Proxy simplifies the interaction with multiple MCP servers by providing a unified interface and toolset.

  • How do I install MCP-Proxy?

You can install it using pip with the command pip install -e . after cloning the repository.

  • Can I add more MCP servers?

Yes! You can configure additional MCP servers in the mcp.json configuration file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
loocor
Star
1
Language
Rust
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)

20 hours ago
Gpt Scrambler

2 days ago