In-depth architectural comparison of the Obsidian Semantic Search and Srclight 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
Obsidian Semantic Search
Databases · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Srclight
Databases · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Obsidian Semantic Search if you need specialized Databases tools running via a local process. Choose Srclight if your workspace requires Databases integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
O
Choose Obsidian Semantic Search when:
You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Incremental indexing with SQLite FTS5 and tree-sitter, Hybrid search combining keyword and embedding results, Support for 11 programming languages and 10 document formats.
Read-only semantic search MCP server for Obsidian vaults using local Ollama embeddings.
Deep code indexing MCP server with SQLite FTS5, tree-sitter, and embeddings. 29 tools for symbol search, call graphs, git intelligence, and hybrid semantic search.
Obsidian Semantic Search is categorized under Databases and uses a local stdio subprocess. In contrast, Srclight belongs to Databases using local stdio subprocess. Select Obsidian Semantic Search when you need capabilities focused on databases and Srclight when you require tools for databases.