EVC Team Relay MCP

What is EVC Team Relay MCP?

EVC Team Relay MCP gives AI agents read/write access to an Obsidian vault through the Team Relay API. It works with Claude Code, Codex CLI, OpenCode, and any MCP‑compatible client.

How to use EVC Team Relay MCP?

Install via uvx (recommended) or from source. Configure your AI tool’s MCP settings with a relay URL (RELAY_CP_URL) and either an agent key (RELAY_AGENT_KEY) or email/password. The server automatically authenticates and refreshes tokens. Once connected, agents can browse shares, list files, read, write, and delete files.

Key features of EVC Team Relay MCP

• Read/write Obsidian vault files via Team Relay API.
• No shell execution – all operations are Python function calls.
• Automatic token management – agent never handles raw tokens.
• Typed parameter validation against JSON Schema.
• Supports stdio and HTTP (remote deployment) transports.
• Compatible with Claude Code, Codex CLI, OpenCode, and other MCP clients.

Use cases of EVC Team Relay MCP

• AI agent reads notes from an Obsidian vault for context.
• Agent creates new notes or documents in a shared folder.
• Agent updates existing files and changes appear in Obsidian instantly.
• Securely integrate AI tools with a self‑hosted collaboration server.

FAQ from EVC Team Relay MCP

What prerequisites are needed?

Python 3.10+ with uv (recommended) or pip, a running EVC Team Relay instance, and a user account on the relay control plane.

How do I authenticate?

Use an agent key (recommended, supports read and write) or an email/password pair. Set RELAY_AGENT_KEY or RELAY_EMAIL/RELAY_PASSWORD in environment variables.

What transports are supported?

Stdio (default when using uvx) and streamable-http for remote deployment. HTTP mode requires running relay_mcp.py --transport http --port 8888 or using Docker Compose.

Where is data stored?

Data resides in the Obsidian vault. Team Relay stores documents as Yjs CRDTs and syncs them to Obsidian clients in real time. The MCP server reads and writes via Team Relay’s REST API.

How is security handled?

No CLI arguments; credentials are passed as environment variables. No shell execution – all calls are typed JSON‑RPC. Token lifecycle is managed internally; the agent never touches raw tokens.