mcp-remote-server
by sirmews
A configurable Model Context Protocol (MCP) server that dynamically loads its capabilities from a remote configuration. It acts as a bridge between MCP clients and remote APIs, leveraging the ModelContextProtocol to create a local server that can communicate with your local MCP client.
Last updated: N/A
What is mcp-remote-server?
mcp-remote-server is a server that dynamically loads its capabilities (tools, resources, and prompts) from a remote configuration specified by a URL. It allows MCP clients to interact with remote APIs through a local server.
How to use mcp-remote-server?
- Set the
MCP_CONTROL_PLANE_URLenvironment variable to the URL of your remote configuration file. - Run the server using
bun run index.ts. - Interact with the server using an MCP client, utilizing the tools, resources, and prompts defined in the remote configuration.
Key features of mcp-remote-server
Dynamic Configuration
Auto-Refresh (every 60 seconds)
Supports All MCP Primitives (Tools, Resources, Prompts)
Uses remote JSON configuration to define server capabilities
Use cases of mcp-remote-server
Integrating remote APIs with MCP clients
Dynamically updating server capabilities without restarting
Exposing remote data as MCP resources
Creating reusable prompt templates for MCP clients
FAQ from mcp-remote-server
What kind of handler endpoints are supported?
What kind of handler endpoints are supported?
Only HTTP/HTTPS handler endpoints are supported.
What format should the configuration file be in?
What format should the configuration file be in?
The configuration must be a JSON file accessible via HTTP GET request.
What format should the handler responses be in?
What format should the handler responses be in?
Handler responses must be JSON-compatible. Tool handlers should return JSON, resource handlers should return content matching the specified mimeType, and prompt handlers should return a string or an array of MCP-formatted messages.
Can I deploy this server to a production environment?
Can I deploy this server to a production environment?
The README states it runs locally only (standard MCP limitation).
How often does the server refresh the configuration?
How often does the server refresh the configuration?
The configuration is automatically refreshed every 60 seconds.