Vault Cortex vs Obsidian Everywhere
A side-by-side look at the Vault Cortex and Obsidian Everywhere MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vault Cortex for knowledge & memory work as a local process; choose Obsidian Everywhere for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Vault Cortex when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
MCP_AUTH_TOKEN, VAULT_PATH.
Choose Obsidian Everywhere when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 52/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Free | Free |
| Required env vars | MCP_AUTH_TOKENVAULT_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 28 | 16 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Vault Cortex | View Obsidian Everywhere |
Tools & capabilities
Vault Cortex tools
No tool names declared yet. Check the project README from the listing page.
Obsidian Everywhere tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Vault Cortex
{
"mcpServers": {
"aliasunder-vault-cortex": {
"command": "npx",
"args": [
"-y",
"vault-cortex@latest"
],
"env": {
"MCP_AUTH_TOKEN": "YOUR_MCP_AUTH_TOKEN_HERE",
"VAULT_PATH": "YOUR_VAULT_PATH_HERE"
}
}
}
}
Obsidian Everywhere
{
"mcpServers": {
"junnnnnw00-obsidian-everywhere": {
"command": "npx",
"args": [
"-y",
"obsidian-everywhere"
]
}
}
}
Frequently asked questions
Vault Cortex is categorized under Knowledge & Memory and uses a local stdio subprocess. Obsidian Everywhere belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Vault Cortex for knowledge & memory work and Obsidian Everywhere for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Vault Cortex is listed as free. Auth: oauth 2.0. Obsidian Everywhere is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aliasunder-vault-cortex and junnnnnw00-obsidian-everywhere as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vault Cortex has a quality signal of 52/100 (Good) with 5 views, 0 installs and 28 GitHub stars. Obsidian Everywhere has 59/100 (Good) with 2 views, 0 installs and 16 GitHub stars.