MCP.so
Sign In

Remote-MCP: Remote MCP Server

@ssut

Basic information

Category

Other

License

MIT

Transports

stdio

Author

ssut

About Remote-MCP: Remote MCP Server

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

Remote-MCP: Remote MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "remote-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@remote-mcp/client"
      ],
      "env": {
        "REMOTE_MCP_URL": "",
        "HTTP_HEADER_Authorization": ""
      }
    }
  }
}

Remote-MCP: Remote MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Remote-MCP?

Remote-MCP is a type-safe, bidirectional, and simple solution for remote Model Context Protocol (MCP) communication. It enables remote access and centralized management of model contexts by bridging local MCP clients with remote MCP servers via tRPC over HTTP. It is designed for developers who need remote MCP capabilities immediately, without waiting for the official MCP roadmap.

How to use Remote-MCP?

Use the client by adding @remote-mcp/client with npx to your MCP client settings (e.g., Claude), setting REMOTE_MCP_URL and optional HTTP_HEADER_Authorization environment variables. For the server, install @remote-mcp/server, create an MCPRouter, add tools and prompts, then start an HTTP server (e.g., standalone Node.js or Cloudflare Workers).

Key features of Remote-MCP

  • Type-safe client/server communication via tRPC
  • Basic MCP command, tool, and prompt support
  • Custom HTTP header support for authentication
  • Easy setup using npx for clients
  • Centralized remote management of MCP resources
  • Supports Cloudflare Workers and Node.js deployments

Use cases of Remote-MCP

  • Connect a local MCP client to a remote set of tools and prompts.
  • Centralize multiple MCP servers behind a single remote endpoint.
  • Give AI assistants access to remote databases or web APIs.
  • Prototype remote MCP setups before official standards are stable.
  • Deploy MCP servers on serverless platforms like Cloudflare Workers.

Frequently asked questions

1

Is Remote-MCP part of the official MCP specification?

No, it is a complementary, early-stage library built on existing MCP concepts. It is not an official implementation.

2

What are the runtime dependencies?

The client requires `@remote-mcp/client` and `@trpc/client@next` plus `zod`. The server requires `@remote-mcp/server` and a tRPC HTTP server adapter.

3

Where does the remote MCP data live?

The remote server runs at the URL configured via `REMOTE_MCP_URL`. Data resides on that server and any resources it connects to (e.g., databases, APIs).

4

What are the known limitations?

The project is experimental; crash-safe handling and complete event subscriptions are not yet implemented. Bidirectional communication (server-to-client requests) is not supported, and there is no built-in authentication middleware (only custom HTTP headers).

5

Which transports are supported?

Communication uses tRPC over HTTP. Examples cover standalone Node.js and Cloudflare Workers adapters.

Comments

More Other MCP servers