Skip to main content

Introduction

Broxy is an MCP proxy that sits between your clients and multiple downstream MCP servers. It aggregates capabilities, applies preset filters, and exposes a single facade so agents only see what you allow.

What Broxy does​

  • Consolidates multiple MCP servers into one endpoint.
  • Filters tools, prompts, and resources with presets.
  • Routes calls with the serverId:tool namespace for deterministic dispatch.
  • Caches capabilities and refreshes them on a schedule.
  • Supports CLI and desktop UI workflows.

Core concepts​

Server An MCP server that exposes tools, prompts, or resources. Servers can be stdio, streamable HTTP, or WebSocket.

Preset A named allow list for tools, prompts, and resources. Presets let you keep task specific toolsets small.

Capabilities The tools, prompts, and resources a server advertises. Broxy fetches and caches these per server.

Namespace Inbound tool calls are always serverId:toolName. The prefix decides which downstream server receives the call.

Flow at a glance​

  1. Define downstream servers in mcp.json.
  2. Create one or more preset_<id>.json files to filter capabilities.
  3. Start the proxy with broxy proxy and the desired preset ID.
  4. Connect your MCP client to the Broxy endpoint.

Next: follow the Quickstart to spin up the proxy and connect your first server.