MCP Obsidian vs MCP Bear
A side-by-side look at the MCP Obsidian and MCP Bear MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Obsidian for knowledge & memory work as a local process; choose MCP Bear 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 MCP Obsidian when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OBSIDIAN_API_KEY.
Choose MCP Bear when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BEAR_API_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 48/100 · Fair | 28/100 · Emerging |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | OBSIDIAN_API_KEY | BEAR_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,489 | 77 |
| Directory activity | 7 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Obsidian | View MCP Bear |
Tools & capabilities
MCP Obsidian tools
No tool names declared yet. Check the project README from the listing page.
MCP Bear 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.
MCP Obsidian
{
"mcpServers": {
"markuspfundstein-mcp-obsidian": {
"command": "uvx",
"args": [
"mcp-obsidian"
],
"env": {
"OBSIDIAN_API_KEY": "YOUR_OBSIDIAN_API_KEY_HERE"
}
}
}
}
MCP Bear
{
"mcpServers": {
"mcp-bear": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/jkawamoto/mcp-bear",
"mcp-bear"
],
"env": {
"BEAR_API_TOKEN": "YOUR_BEAR_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
MCP Obsidian is categorized under Knowledge & Memory and uses a local stdio subprocess. MCP Bear belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Obsidian for knowledge & memory work and MCP Bear 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.
MCP Obsidian is listed as free. Auth: api key required. MCP Bear has no declared pricing — check the project's own site. 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 markuspfundstein-mcp-obsidian and mcp-bear as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Obsidian has a quality signal of 48/100 (Fair) with 7 views, 0 installs and 4,489 GitHub stars. MCP Bear has 28/100 (Emerging) with 0 views, 0 installs and 77 GitHub stars.