Master Mcp Server

Created By
Jakedismo9 months ago
Master MCP Server Master MCP Server aggregates multiple MCP servers behind a single, secure endpoint. It provides configuration-driven module loading, unified capability discovery, request routing with resilience, and first-class OAuth flows for multi-backend authentication. # Highlights - Aggregates multiple MCP servers with tool/resource discovery and namespacing - OAuth support: master token pass-through, delegated provider flows, proxy refresh - Config-driven setup with JSON/YAML, schema validation, and secret resolution - Resilient routing: load-balancing, retries with backoff/jitter, circuit-breakers - Cross-platform: Node.js server and Cloudflare Workers runtime - Production-ready deployment: Docker, Cloudflare Workers, Koyeb - Testing strategy and CI-ready structure
Overview

what is Master MCP Server?

Master MCP Server aggregates multiple MCP servers behind a single, secure endpoint, providing configuration-driven module loading, unified capability discovery, request routing with resilience, and OAuth flows for multi-backend authentication.

how to use Master MCP Server?

To use Master MCP Server, install the dependencies, configure the environment, and run it in development mode. You can access health metrics and MCP endpoints for various operations.

key features of Master MCP Server?

  • Aggregates multiple MCP servers with tool/resource discovery and namespacing
  • OAuth support for master token pass-through and delegated provider flows
  • Config-driven setup with JSON/YAML, schema validation, and secret resolution
  • Resilient routing with load-balancing and circuit-breakers
  • Cross-platform compatibility with Node.js and Cloudflare Workers
  • Production-ready deployment options including Docker and Cloudflare Workers

use cases of Master MCP Server?

  1. Centralizing multiple backend services under a single endpoint
  2. Implementing OAuth authentication for secure access
  3. Load balancing and routing requests to various MCP servers

FAQ from Master MCP Server?

  • What is the purpose of Master MCP Server?

It aggregates multiple MCP servers to provide a unified and secure interface for backend services.

  • Is it easy to deploy Master MCP Server?

Yes! It supports Docker and Cloudflare Workers for easy deployment.

  • Can I customize the configuration?

Yes! The setup is configuration-driven, allowing customization through JSON/YAML.

Server Config

{
  "mcpServers": {
    "master-mcp-server": {
      "url": "http://localhost:3000"
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Jakedismo
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

5 hours ago