drio
Open app

Remote-MCP: Remote Model Context Protocol

Source

A type-safe solution to remote MCP communication, enabling effortless integration for centralized management of Model Context.

Catalog onlyCatalog onlySTDIO

Overview

Remote-MCP is a type-safe solution for remote Model Context Protocol (MCP) communication, enabling centralized management of model contexts and remote access to MCP servers.

To use Remote-MCP, you can either use the publicly published package by configuring your MCP client settings or code your own local MCP server using the provided libraries.

  • Type-safe bidirectional communication between MCP clients and servers. - Easy integration with existing MCP setups. - Support for remote access to model contexts. - Basic error handling and logging capabilities.
  1. Connecting local MCP clients to remote MCP servers for centralized management.
  2. Implementing remote access for applications requiring model context management.
  3. Developing custom tools and services that utilize the MCP framework.

Add to your AI client

Use these steps to connect Remote-MCP: Remote Model Context Protocol in Cursor, Claude, VS Code, and other MCP-compatible apps. The same JSON appears in the Use with menu above for one-click copy.

Cursor

Add this to your .cursor/mcp.json file in your project root, then restart Cursor.

.cursor/mcp.json

{
  "mcpServers": {
    "remote-mcp-ssut": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-remote-mcp-ssut"
      ]
    }
  }
}

Claude Desktop

Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

{
  "mcpServers": {
    "remote-mcp-ssut": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-remote-mcp-ssut"
      ]
    }
  }
}

Claude Code

Add this to your project's .mcp.json file. Claude Code will detect it automatically.

.mcp.json (project root)

{
  "mcpServers": {
    "remote-mcp-ssut": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-remote-mcp-ssut"
      ]
    }
  }
}

VS Code (Copilot)

Add this to your .vscode/mcp.json file. Requires the GitHub Copilot extension with MCP support enabled.

.vscode/mcp.json

{
  "servers": {
    "remote-mcp-ssut": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-remote-mcp-ssut"
      ]
    }
  }
}

Windsurf

Add this to your Windsurf MCP config file, then restart Windsurf.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "remote-mcp-ssut": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-remote-mcp-ssut"
      ]
    }
  }
}

Cline

Open Cline settings, navigate to MCP Servers, and add this server configuration.

Cline MCP Settings (via UI)

{
  "mcpServers": {
    "remote-mcp-ssut": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-remote-mcp-ssut"
      ]
    }
  }
}

FAQ

Is Remote-MCP stable for production use?

The project is currently under active development and is considered experimental. Expect breaking changes and potential issues.

How can I contribute to Remote-MCP?

Contributions are welcome! Please refer to the CONTRIBUTING.md file for details.

What is the license for Remote-MCP?

This project is licensed under the MIT License.

Developer tools