evc-team-relay-mcp

Overview

MCP server that enables reading and writing documents in an Obsidian vault through the EVC Team Relay protocol. It acts as a bridge between MCP-compatible agents and Obsidian knowledge bases.

Best for

Best for
Developers using EVC Team Relay who want MCP-based access to their Obsidian knowledge base

Use cases

• Reading Obsidian notes as context for AI agents
• Writing AI-generated summaries or entries to a vault
• Syncing structured data between external tools and Obsidian

How to use

Tools exposed

• RELAY_CP_URL
• RELAY_AGENT_KEY
• RELAY_EMAIL
• RELAY_PASSWORD
• list_shares
• list_files
• read_file
• upsert_file
• delete_file
• read_document
• write_document
• authenticate

Tested with

Claude Code, Codex CLI, OpenCode

Example client config

{\n  "mcpServers": {\n    "evc-relay": {\n      "command": "uvx",\n      "args": ["evc-team-relay-mcp"],\n      "env": {\n        "RELAY_CP_URL": "https://cp.yourdomain.com",\n        "RELAY_AGENT_KEY": "tr_agent_your_key_here"\n      }\n    }\n  }\n}

Notes

MCP server that enables reading and writing documents in an Obsidian vault through the EVC Team Relay protocol. It acts as a bridge between MCP-compatible agents and Obsidian knowledge bases.

2 stars on GitHub. Last updated 2026-05-31. Licensed MIT.

Use cases

• Reading Obsidian notes as context for AI agents
• Writing AI-generated summaries or entries to a vault
• Syncing structured data between external tools and Obsidian

Pros

• Connects Obsidian vaults directly to MCP tools without custom scripting
• Supports both read and write operations for full interaction
• Written in Python, easy to inspect and modify

Cons

• Requires an active EVC Team Relay service to function
• Low star count (2) suggests minimal community testing or documentation
• Limited to Obsidian vaults; no support for other note formats

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.