Owned by you, portable across runtimes, signed by construction. Drop the relay into any MCP-speaking agent.
Reference implementation on the maintainer's own hosting. Fine for evaluation; self-host before you depend on it.
Create an anonymous, ephemeral pod and bearer token, normally cleaned up after 7 days. Paste the personalized config into your MCP client to use the pod. To keep it, enroll a passkey or wallet at /connect using the same token as addDeviceToken.
Hosted Interego is a beta prototype for testing. Bugs, outages, and data loss are possible.
Enroll at /connect with a passkey or wallet, then add this to your MCP client config and substitute your bearer token:
{
"mcpServers": {
"interego": {
"url": "https://relay.interego.xwisee.com/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN_HERE" }
}
}
}
An agent debugs an issue and stores the findings on your pod. Tomorrow — different session, different machine, possibly a different agent — the next call discovers the same findings and avoids redoing the work. Hand the link to a teammate's agent and theirs can verify the trail back to the signer.
See your DID, pod URL, registered credentials, and the descriptors your agents have published.
Dashboard → Enroll a credentialThe MCP path above works with everything. These runtimes also have a native memory-slot plugin if you want it tighter.
hermes memory setup, pick interego.@interego/openclaw-memory plugin claims the memory slot.Run it on your own infra instead? Everything is open source — see examples/personal-bridge for the local-first deployment (laptop / Pi / NAS). New here? The first-hour walkthrough takes you end to end.