os-mcplisted
Install: claude install-skill naveedharri/benai-skills
# OS MCP — Railway Deploy
This skill deploys the Relay MCP v2 server to the user's own Railway account. The MCP source is bundled at `${CLAUDE_PLUGIN_ROOT}/skills/os-mcp/reference/relay-mcp-server/` — copy from there, do not fetch from anywhere else. The deployed server lets Claude clients (Claude Code or claude.ai) read/write the user's Obsidian vault by talking to the Relay.md sync protocol.
## What the user provides
**One thing: a Railway account token** — created at `https://railway.com/account/tokens`.
That's it. After deploy, the user signs in with their Relay.md credentials via OAuth; the MCP then auto-discovers their relay vault and the folders inside it via PocketBase. No vault GUIDs, no folder maps.
## Values set automatically by the skill
| Var | Source | Value |
|-----|--------|-------|
| `RELAY_API_URL` | preset | `https://api.system3.md` |
| `PB_AUTH_URL` | preset | `https://auth.system3.md` |
| `PB_COLLECTION` | preset | `users` |
| `DATA_DIR` | preset | `/data` |
| `PORT` | preset | `3000` |
| `JWT_SECRET` | auto-generated | `openssl rand -hex 32` |
| `STATIC_MCP_BEARER` | auto-generated | `openssl rand -hex 24` |
| `ALLOWED_EMAILS` | preset | *blank* (any authenticated Relay.md user) |
| `RELAY_AUTH_TOKEN` | preset | *blank* (OAuth-only; no static fallback) |
| `RELAY_ID` | not set | *auto-discovered at runtime per user* |
| `PUBLIC_URL` | derived | from `railway domain` after first deploy |
Save the generated `STATIC_MCP_BEARER` in the chat for the us