Evc Team Relay MCP

What evc-team-relay-mcp MCP server does

The evc-team-relay-mcp MCP server exposes Team Relay file operations to MCP-compatible AI clients. It is intended for Obsidian vault workflows backed by Team Relay, where an agent needs to inspect available shares, browse files, read file contents, or create and update files.

The working workflow is share-oriented: the client can list accessible shares, identify files within a folder share, read a file by path, and use upsert_file to create or replace a file. The server does not provide unrestricted local filesystem access; operations go through the configured Team Relay control plane.

Several names shown in the tool list are not currently usable. read_document, write_document, and delete_file have no backend route and always raise an error. The supported write operation is upsert_file, not write_document.

How it works

The evc-team-relay-mcp MCP server runs as a local stdio process by default. MCP clients start it with uvx, and the process communicates with the client over MCP. It can also run as an HTTP server for a shared or server-side deployment.

Set RELAY_CP_URL to the Team Relay control-plane base URL. Authentication uses either an agent key or an email/password account. Agent-key authentication enables the working folder-share read and write operations. Email/password authentication uses JWT-based access and is read-only for the supported file tools.

Authentication, token refresh, and token lifecycle management are handled by the server. A typical sequence is list_shares, list_files, then read_file or upsert_file.

Setup and configuration

Install-free execution is available through the Python package runner:

uvx evc-team-relay-mcp

Configure the MCP client with RELAY_CP_URL and one credential method. For agent-key mode, provide RELAY_AGENT_KEY. For account authentication, provide both RELAY_EMAIL and RELAY_PASSWORD.

The project documents configuration examples for Claude Code, Codex CLI, and OpenCode. Source installation is also supported with uv sync or pip install . after cloning the repository.

For HTTP deployment, the server can be started with --transport http and a port. It binds to 127.0.0.1 by default. Remote clients can connect through an SSH tunnel, while binding to another interface requires explicitly setting --host. The HTTP endpoint has no built-in authentication, so public binding should be protected by a reverse proxy or firewall.

Tools and capabilities

Working capabilities include:

• authenticate for automatic credential handling
• list_shares with share-kind and ownership filtering
• list_files for browsing folder shares
• read_file for reading a file by path
• upsert_file for creating or updating a file in agent-key mode

The server also declares read_document, write_document, and delete_file, but these operations are currently unavailable because the Team Relay control plane lacks the required routes. tr_search is available in JWT mode according to the documented availability matrix, although it is not part of the typical folder-file workflow.

Limitations and notes

The evc-team-relay-mcp MCP server does not make document-share live content available through REST; that content uses a CRDT/WebSocket path instead. Switching from email/password to an agent key will not fix the unavailable document and delete operations. It only enables the supported upsert_file write route.

The HTTP MCP endpoint does not authenticate incoming clients itself. Keep the default localhost binding where possible, or place any network-facing deployment behind appropriate access controls. The project is released under the MIT license.