MCP server with 40 tools for AI agents. Memory, web fetch, search, file ops, screenshots, and multi-agent coordination in one Go binary.
MCPpedia last refreshed this data
Relay is an MCP server that MCP server with 40 tools for AI agents. Memory, web fetch, search, file ops, screenshots, and multi-agent coordination in one Go binary. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 88/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"relay": {
"command": "relay"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
One MCP server for files, images, PDFs, web, and workflows. Your files stay local. No telemetry. No account. No cloud.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked userelay against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
An autonomous agent that conducts deep research on any data using any LLM providers
1000+ scientific tools for AI scientists: life science, reserach, literature, and more.
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Security Weekly
Get CVE alerts and security updates for Relay and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
One MCP server for files, images, PDFs, web, and workflows. Your files stay local. No telemetry. No account. No cloud.
Run it with npx userelay.
npx userelay
That opens the setup wizard, downloads the right binary, and configures your editor. No install needed.
If you already have it:
npx userelay - launch the TUI menunpx userelay init - reconfigure your editornpx userelay status - check version and toolsnpx userelay --help - see all commandsSee the full comparison against standalone MCP servers.
Every MCP server does one thing. File server. Image server. PDF server. Web fetch server. You stitch 5 of them together and each one has its own install, its own config, its own update cycle, its own way of breaking.
Relay is one binary with 40 tools across 7 categories. One install. One config. One process. When it breaks, you know which thing broke.
| Relay | Multiple servers | |
|---|---|---|
| Install | npx userelay | One per server |
| Config | One entry | One per server |
| Updates | One binary | One per server |
| Memory | One process | N processes |
| Tools | 40 built-in | Whatever you assembled |
npx userelay tui
Runs locally. Your files stay on your machine. Type q to exit.
--http.ANTHROPIC_API_KEY is present.No pile of single-purpose servers. One binary.
Use status first if you want a one-shot command instead of starting the stdio server.
npx userelay status
relay v0.3.0
tools: 40 registered (7 categories)
transport: stdio (default) | http (with --http)
npx userelay init --list
relay init --list
detected editors:
1. Cursor
2. VS Code
If your editor is listed, write the config:
npx userelay init
If you installed Relay from source or a release, relay status prints the same shape:
relay status
╭─────────────────────────────────╮
│ relay vde
... [View full README on GitHub](https://github.com/valtors/relay#readme)