MCP Servers
evc-team-relay-mcp
MCP server for reading and writing Obsidian vault documents via EVC Team Relay
Our verdict
We have not reviewed evc-team-relay-mcp yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About evc-team-relay-mcp
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
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
Notes
2 stars on GitHub. Last updated 2026-05-31. Licensed MIT.
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
Key facts
What we have checked
Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Tools exposed
RELAY_CP_URLRELAY_AGENT_KEYRELAY_EMAILRELAY_PASSWORDlist_shareslist_filesread_documentwrite_documentdelete_file
Clients the listing names (not checked here)
Claude Code
Example client config
{
"mcpServers": {
"evc-relay": {
"command": "uvx",
"args": [
"evc-team-relay-mcp"
],
"env": {
"RELAY_CP_URL": "https://cp.yourdomain.com",
"RELAY_AGENT_KEY": "tr_agent_your_key_here"
}
}
}
}Install
Add evc-team-relay-mcp to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --env RELAY_CP_URL=YOUR_RELAY_CP_URL --transport stdio evc-team-relay-mcp -- uvx evc-team-relay-mcp@1.0.9Needs RELAY_CP_URL: replace each YOUR_ value with your own.
Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"evc-team-relay-mcp": {
"command": "uvx",
"args": [
"evc-team-relay-mcp@1.0.9"
],
"env": {
"RELAY_CP_URL": "YOUR_RELAY_CP_URL"
}
}
}
}Needs RELAY_CP_URL: replace each YOUR_ value with your own.
Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"evc-team-relay-mcp": {
"command": "uvx",
"args": [
"evc-team-relay-mcp@1.0.9"
],
"env": {
"RELAY_CP_URL": "YOUR_RELAY_CP_URL"
}
}
}
}Needs RELAY_CP_URL: replace each YOUR_ value with your own.
VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"inputs": [
{
"type": "promptString",
"id": "relay-cp-url",
"description": "URL of the Team Relay control plane (e.g. https://cp.yourdomain.com)",
"password": true
}
],
"servers": {
"evc-team-relay-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"evc-team-relay-mcp@1.0.9"
],
"env": {
"RELAY_CP_URL": "${input:relay-cp-url}"
}
}
}
}Needs RELAY_CP_URL: replace each YOUR_ value with your own.
Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.evc-team-relay-mcp]
command = "uvx"
args = ["evc-team-relay-mcp@1.0.9"]
env_vars = ["RELAY_CP_URL"]Needs RELAY_CP_URL: replace each YOUR_ value with your own.
- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What evc-team-relay-mcp connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 1.0.9Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 1.0.9Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 1.0.9Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 1.0.9Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 1.0.9Config checked | Codex docs |
Alternatives
Alternatives to evc-team-relay-mcp
| Record | Type | How we know | Checked |
|---|---|---|---|
| oraios/serenaThis is an alternative to it | MCP server | Named in the listing | Not dated |
Compare
Compare evc-team-relay-mcp side by side
Sources
Where this comes from
No sources recorded yet. Each source we check is listed here with the date we checked it.
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Open-source & AI alternatives
Swap-in tools that solve the same job. Weigh the trade-offs before you commit.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.