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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago