mcp-remote

mcp-remote-server acts as a bridge between MCP clients and remote APIs by loading its capabilities from a remote configuration. It periodically fetches a JSON configuration from the URL specified by MCP_CONTROL_PLANE_URL (auto-refresh every 60 seconds) which describes tools, resources, and prompts that the local MCP client can access. Tools allow you to execute actions via remote API calls, resources expose remote data as readable content, and prompts define reusable prompt templates that can be invoked by the MCP client. To use it, point the server at your remote configuration and run the server so your MCP client can query the local MCP endpoint and discover available capabilities. Tools will respond with JSON payloads that are wrapped into MCP tool responses, resources return content matching their mime types, and prompts yield either plain strings or arrays of MCP-formatted messages depending on the remote handler’s response.

Prerequisites:

• Node.js installed (or Bun, as used by this project)
• Access to the internet to fetch packages

Installation steps:

1. Install Bun (if not already installed): curl https://bun.sh/install | bash export Bun_Version=$(bun -v)
2. Install dependencies (or rely on the remote configuration via npx): bun install
3. Ensure you have a valid MCP_CONTROL_PLANE_URL environment variable pointing to your remote configuration endpoint.
4. Start the server as described in the README configuration, for example by using the mcp_config entry: npm or npx approach depending on your setup. For example: npx -y sirmews-mcp-remote-server or follow the project’s standard start command if provided (e.g., bun run index.ts).

Notes:

• The server expects HTTP/HTTPS endpoints from the remote config and will fetch the configuration at regular intervals (default 60 seconds).

Environment variable MCP_CONTROL_PLANE_URL must be reachable over HTTP(S) and return a JSON configuration with keys: tools, resources, prompts. Each tool/resource/prompt must include a handler URL. Tool responses are JSON that will be wrapped by the MCP tool response, resources return content matching their mimeType, and prompts return either a string or an array of MCP-formatted messages. The server auto-refresh cadence can typically be adjusted in the code or via config if exposed; ensure your remote config is accessible and CORS policies allow the local server to fetch it. If you encounter issues, verify that the remote endpoints are HTTP/HTTPS accessible and that the remote configuration conforms to the documented schema.