MCP server proxy

Created By
12beama year ago
Extend MCP server functionality to work as a worker
Overview

what is MCP server proxy?

MCP server proxy is a tool designed to extend the functionality of MCP servers, allowing them to operate as workers that can handle messages efficiently.

how to use MCP server proxy?

To use the MCP server proxy, you need to import the proxyMessage function from the package and create a server instance. You can then configure message handlers to pass messages to the existing MCP server.

key features of MCP server proxy?

  • Extends MCP server capabilities to work as a worker
  • Allows for efficient message handling between clients and servers
  • Written in TypeScript for type safety and modern development practices

use cases of MCP server proxy?

  1. Enhancing existing MCP servers with additional message processing capabilities.
  2. Creating scalable applications that require multiple workers to handle messages.
  3. Integrating with other services that communicate through MCP servers.

FAQ from MCP server proxy?

  • What programming language is MCP server proxy written in?

MCP server proxy is written in TypeScript, ensuring type safety and modern coding standards.

  • Is there any licensing information available?

The project does not specify a license at this time.

  • How can I contribute to the MCP server proxy?

Contributions can be made through the GitHub repository at https://github.com/12beam/cd-mcp-proxy.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
12beam
Star
1
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