What is an MCP Server?

An MCP (Model Context Protocol) server acts as a bridge, allowing AI models to access and interact with external data sources and tools. It standardizes how applications provide context to LLMs.

Why would I need an MCP Aggregator?

An MCP Aggregator is useful for combining multiple MCP servers into a single interface. This helps overcome limitations in clients (like Cursor) that restrict the number of concurrent MCP connections, simplifies configuration, and resolves potential tool name conflicts.

How does the MCP Aggregator work?

The MCP Aggregator functions as both an MCP server (to the client) and an MCP client (to the backend servers). It receives requests from the client, routes them to the appropriate backend server, and aggregates the responses before returning them to the client.

What is tool name sanitization?

Tool name sanitization is the process of replacing dashes with underscores in tool names. This is necessary because some clients, like Cursor, have issues with tools that contain dashes in their names. The MCP Aggregator performs this sanitization automatically.

How do I configure the MCP Aggregator?

The MCP Aggregator is configured using a JSON file (e.g., config.json). This file defines the connection details for each backend MCP server, including the command to execute, arguments, environment variables, and optional tool filtering rules.

What are the available deployment options?

The MCP Aggregator can be deployed using several methods, including:

• Installation script
• go install
• Docker
• Makefile

What environment variables does the MCP Aggregator support?

The MCP Aggregator supports the following environment variables:

• MCP_CONFIG: Path to the configuration file (required)
• MCP_LOG_LEVEL: Logging level (error, info, debug, trace) - default: info
• MCP_LOG_FILE: Path to the log file
• MCP_PROTOCOL_VERSION: Force a specific protocol version for compatibility
• MCP_CURSOR_MODE: Enable Cursor-specific compatibility adjustments

How does the MCP Aggregator integrate with UBOS?

The MCP Aggregator integrates seamlessly with the UBOS platform, enabling you to leverage the full power of UBOS for AI agent development, orchestration, and deployment.

What is tool filtering, and how do I use it?

Tool filtering allows you to selectively expose tools from each backend MCP server. To enable tool filtering, add a tools object to your server configuration with an allowed array listing the tools you want to expose. This can help to limit the number of exposed tools, avoid name conflicts, and improve performance.