In-depth architectural comparison of the Evc Team Relay MCP and Obsidian MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Evc Team Relay MCP
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: other
Obsidian MCP
Knowledge & Memory · Local stdio
Quality: 47/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Evc Team Relay MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Obsidian MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Evc Team Relay MCP when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: RELAY_CP_URL, RELAY_AGENT_KEY, RELAY_EMAIL, RELAY_PASSWORD.
Give AI agents read/write access to your Obsidian vault via MCP
Self-hosted MCP server for Obsidian with semantic + full-text search over PostgreSQL/pgvector, wikilink graph traversal, atomic note CRUD, OAuth 2.0, and a self-describing vault guide.
Evc Team Relay MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Obsidian MCP belongs to Knowledge & Memory using local stdio subprocess. Select Evc Team Relay MCP when you need capabilities focused on knowledge & memory and Obsidian MCP when you require tools for knowledge & memory.
Primary tools included: Semantic and full-text search via PostgreSQL with pgvector, Atomic CRUD operations on markdown notes, Wikilink graph traversal for contextual navigation.