Remote MCP, without exposed device ports
Your computers.
Available to MCP.
Pair a device once. ReMCP routes authenticated tool calls to its local agent while the device keeps an outbound-only connection.
Private by default
Accounts and devices are isolated by authenticated user identity and revocable device credentials.
No inbound laptop port
The device agent connects outward to ReMCP. Your laptop does not need a public IP or open listener.
Explicit control
Read, write and destructive tools declare their behavior so MCP clients can apply the right review flow.
Workspace
Pair and manage devices
Sign in to generate one-time pairing commands and revoke computers you no longer trust.
Account
Authenticate with Firebase to access your device workspace.
MCP endpoint
Use this HTTPS endpoint when adding ReMCP to an MCP client.
https://remcp.delio24.com/mcp- Transport
- Streamable HTTP
- Authentication
- OAuth 2.1 + PKCE
Add a computer
Generate a one-time pairing command
The code expires automatically and can only be claimed once.
Paired devices
Online state updates when the page refreshes.Self-hostable architecture
Keep the relay yours.
ReMCP can run as a small Docker service while each computer runs its own local agent.
Review the security model