Smart Connections MCP Server
Provides semantic search, similarity matching, connection graphs, and note content access for Obsidian vaults using pre-computed embeddings from the Smart Connections plugin.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Smart Connections MCP Server search my vault for notes about artificial intelligence"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Smart Connections MCP Server
A Model Context Protocol (MCP) server that provides semantic search and knowledge graph capabilities for Obsidian vaults using Smart Connections embeddings.
Fork note: this is a fork maintained by A Portland Career for its second-brain pilot kit, based on the original
smart-connections-mcpby Daniel Glickman (MIT). It adds true semanticsearch_notes(embeds the query with the vault's model instead of literal keyword matching); see "Query embedding" below. Original copyright and MIT license preserved inLICENSE.
Overview
This MCP server allows Claude (and other MCP clients) to:
Search semantically through your Obsidian notes using pre-computed embeddings
Find similar notes based on content similarity
Build connection graphs showing how notes are related
Query by embedding vectors for advanced use cases
Access note content with block-level granularity
Related MCP server: Smart Connections MCP Server
Features
π Semantic Search
Uses the embeddings generated by Obsidian's Smart Connections plugin to perform fast, accurate semantic searches across your entire vault.
πΈοΈ Connection Graphs
Builds multi-level connection graphs showing how notes are related through semantic similarity, helping discover hidden relationships in your knowledge base.
π Vector Similarity
Direct access to embedding-based similarity calculations using cosine similarity on 384-dimensional vectors (TaylorAI/bge-micro-v2 model).
π Content Access
Retrieve full note content or specific sections/blocks with intelligent extraction based on Smart Connections block mappings.
Installation
Prerequisites
Node.js 18 or higher
An Obsidian vault with Smart Connections plugin installed and embeddings generated
Claude Desktop (or another MCP client)
Setup
Clone the repository:
git clone https://github.com/bookbran/smart-connections-mcp.git cd smart-connections-mcpInstall dependencies:
npm installBuild the TypeScript project:
npm run buildConfigure Claude Desktop:
Edit your Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the following to the
mcpServerssection:{ "mcpServers": { "smart-connections": { "command": "node", "args": [ "/ABSOLUTE/PATH/TO/smart-connections-mcp/dist/index.js" ], "env": { "SMART_VAULT_PATH": "/ABSOLUTE/PATH/TO/YOUR/OBSIDIAN/VAULT" } } } }Important: Replace the paths with your actual paths:
Update the
argspath to point to your builtindex.jsfileUpdate
SMART_VAULT_PATHto your Obsidian vault path
Restart Claude Desktop
The MCP server will automatically start when Claude Desktop launches.
Available Tools
1. get_similar_notes
Find notes semantically similar to a given note.
Parameters:
note_path(string, required): Path to the note (e.g., "Note.md" or "Folder/Note.md")threshold(number, optional): Similarity threshold 0-1, default 0.5limit(number, optional): Maximum results, default 10
Example:
{
"note_path": "MyNote.md",
"threshold": 0.7,
"limit": 5
}Returns:
[
{
"path": "RelatedNote.md",
"similarity": 0.85,
"blocks": ["#Overview", "#Key Points", "#Details"]
}
]2. get_connection_graph
Build a multi-level connection graph showing how notes are semantically connected.
Parameters:
note_path(string, required): Starting note pathdepth(number, optional): Graph depth (levels), default 2threshold(number, optional): Similarity threshold 0-1, default 0.6max_per_level(number, optional): Max connections per level, default 5
Example:
{
"note_path": "MyNote.md",
"depth": 2,
"threshold": 0.7
}Returns:
{
"path": "MyNote.md",
"depth": 0,
"similarity": 1.0,
"connections": [
{
"path": "RelatedNote.md",
"depth": 1,
"similarity": 0.82,
"connections": [...]
}
]
}3. search_notes
Semantic search by text query. Embeds the query with the same model used for the vault's note embeddings (bge-micro-v2) and ranks notes by cosine similarity, so it matches by meaning rather than exact words. Falls back to a multi-term keyword search if the embedding model can't be loaded (e.g. fully offline before the model has ever been cached).
First-query note: the query-embedding model is downloaded from the Hugging Face hub on the first
search_notescall of a server session (needs network once, ~30s), then cached undernode_modules/@huggingface/transformers/.cacheso every later call is offline and fast (~4ms). See "Query embedding" under Technical Details.
Parameters:
query(string, required): Search query textlimit(number, optional): Maximum results, default 10threshold(number, optional): Similarity threshold 0-1, default 0.4 (typical relevant matches score ~0.4-0.75; lower to widen recall)
Example:
{
"query": "project management",
"limit": 5
}4. get_embedding_neighbors
Find nearest neighbors for a given embedding vector (advanced use).
Parameters:
embedding_vector(number[], required): 384-dimensional vectork(number, optional): Number of neighbors, default 10threshold(number, optional): Similarity threshold 0-1, default 0.5
5. get_note_content
Retrieve full note content with optional block extraction.
Parameters:
note_path(string, required): Path to the noteinclude_blocks(string[], optional): Specific block headings to extract
Example:
{
"note_path": "MyNote.md",
"include_blocks": ["#Introduction", "#Main Points"]
}Returns:
{
"content": "# Full note content...",
"blocks": {
"#Introduction": "Content of this section...",
"#Main Points": "Content of this section..."
}
}6. get_stats
Get statistics about the knowledge base.
Parameters: None
Returns:
{
"totalNotes": 137,
"totalBlocks": 1842,
"embeddingDimension": 384,
"modelKey": "TaylorAI/bge-micro-v2"
}Usage Examples
Once configured, you can ask Claude to use these tools naturally:
"Find notes similar to my project planning document"
"Show me a connection graph starting from my main research note"
"Search my notes for information about [your topic]"
"What's in my note about [topic]?"
"Give me stats about my knowledge base"
Architecture
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Claude Desktop β
β (MCP Client) β
βββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββββββ
β
β MCP Protocol (stdio)
β
βββββββββββββββββββββββββββΌββββββββββββββββββββββββββββββββββββ
β Smart Connections MCP Server β
β βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β index.ts (MCP Server + Tool Handlers) β β
β ββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββββ β
β β β
β ββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββ β
β β search-engine.ts (Semantic Search Logic) β β
β β - getSimilarNotes() β β
β β - getConnectionGraph() β β
β β - searchByQuery() β β
β ββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββββ β
β β β
β ββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββ β
β β smart-connections-loader.ts (Data Access) β β
β β - Load .smart-env/smart_env.json β β
β β - Load .smart-env/multi/*.ajson embeddings β β
β β - Read note content from vault β β
β ββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββββ β
β β β
β ββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββ β
β β embedding-utils.ts (Vector Math) β β
β β - cosineSimilarity() β β
β β - findNearestNeighbors() β β
β βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
βββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββββββ
β
β File System Access
β
βββββββββββββββββββββββββββΌββββββββββββββββββββββββββββββββββββ
β Obsidian Vault + .smart-env/ β
β - smart_env.json (config) β
β - multi/*.ajson (embeddings for 137 notes) β
β - *.md (markdown note files) β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββTechnical Details
Embedding Model
Model: TaylorAI/bge-micro-v2
Dimensions: 384
Similarity Metric: Cosine similarity
Query embedding (search_notes)
get_similar_notes / get_connection_graph compare notes against each other using the vectors Smart Connections already stored, so they need no model at runtime. search_notes is different: it must turn an arbitrary text query into a vector to compare against those stored vectors. It does this with @huggingface/transformers (transformers.js), loading the same model the vault is configured for (read from smart_env.json, e.g. TaylorAI/bge-micro-v2) so the query and note vectors live in the same space.
The model repo is tried in order: the vault's configured
model_key, thenSC_EMBED_MODEL(env override), thenTaylorAI/bge-micro-v2, thenXenova/bge-micro-v2.ONNX weights download from the Hugging Face hub on first use and are cached under
node_modules/@huggingface/transformers/.cache. Firstsearch_notescall: ~30s; subsequent calls: ~4ms, offline.If no model can be loaded (offline with an empty cache),
search_notestransparently falls back to a multi-term keyword search so it still returns useful results.Override the model with the
SC_EMBED_MODELenv var if your vault uses a different embedding model. It must be a bge-micro-v2-family model, or the query vectors won't match the stored note vectors.
Data Format
The server reads from Obsidian's Smart Connections .smart-env/ directory:
smart_env.json: Configuration and model settingsmulti/*.ajson: Per-note embeddings and block mappings
Performance
Load time: ~2-5 seconds for 137 notes
Search: Near-instant (<50ms) using pre-computed embeddings
Memory: ~20-30MB for embeddings + note index
Development
Build
npm run buildWatch Mode
npm run watchRun Locally
export SMART_VAULT_PATH="/path/to/your/vault"
npm run devProject Structure
smart-connections-mcp/
βββ src/
β βββ index.ts # MCP server & tool handlers
β βββ search-engine.ts # Semantic search logic
β βββ smart-connections-loader.ts # Data loading
β βββ embedding-utils.ts # Vector math utilities
β βββ types.ts # TypeScript type definitions
βββ dist/ # Compiled JavaScript (generated)
βββ package.json
βββ tsconfig.json
βββ README.mdTroubleshooting
"Smart Connections directory not found"
Ensure your vault has the Smart Connections plugin installed
Verify embeddings have been generated (check
.smart-env/multi/directory)Check that
SMART_VAULT_PATHpoints to the correct vault
"Configuration file not found"
Run Smart Connections in Obsidian at least once to generate configuration
Check for
.smart-env/smart_env.jsonin your vault
"No embeddings found for note"
Some notes may not have embeddings if they're too short (< 200 chars)
Re-run Smart Connections embedding generation in Obsidian
Server not appearing in Claude Desktop
Verify the configuration file syntax (JSON must be valid)
Check the file paths are absolute paths, not relative
Restart Claude Desktop completely
Check Claude Desktop logs for error messages
License
MIT
Author
Original: Daniel Glickman (msdanyg/smart-connections-mcp)
Fork maintained by: A Portland Career (semantic
search_notes+ pilot-kit integration)
Acknowledgments
Built for use with Obsidian
Integrates with Smart Connections plugin
Uses Model Context Protocol by Anthropic
Available Tools
10 toolscheck_search_healthA
Positive control for retrieval. Asks the index for notes that are known to be there, by their own titles, and reports whether they come back. Use this at session start, before trusting any empty search result, and any time a vault has been quiet or moved between machines. Returns alive (false means every empty result from this server is untrustworthy), verdict (a plain-language line written to be read aloud), mode, coverage, and the individual probes. A retrieval tool that can return nothing must be able to prove it can still see.
Inputs: canary_path.
check_vault_integrityA
Find wikilinks that point at notes which do not exist. Git proves two machines agree on what is COMMITTED; it is silent about a note written outside the vault folder or written on another machine and never committed, and both fail the same silent way, as a link that resolves to nothing. Results are ranked by how many DISTINCT notes reference each missing target, because one note pointing at an unwritten note is an ordinary forward reference while six pointing at the same target means the vault treats it as real and it is either a concept that never got a home note or a note this machine cannot see. Run at session start alongside check_search_health.
Inputs: min_references.
get_backlinksA
Which notes explicitly link TO this one. This answers a different question from semantic search: backlinks are edges the author wrote by hand, so they show what the vault has decided this note is load-bearing for, regardless of whether the prose is similar. Use it to judge how important a note is, to find every place a decision is cited before changing it, and to trace how a concept actually gets used. Set include_outbound to also get what this note links to.
Inputs: note_path (required), include_outbound.
get_connection_graphA
Build a multi-level connection graph starting from a note, showing how notes are semantically connected.
Inputs: note_path (required), depth, threshold, max_per_level.
get_embedding_neighborsB
Find nearest neighbors for a given embedding vector. Useful for custom similarity searches.
Inputs: embedding_vector (required), k, threshold.
get_note_contentA
Retrieve the full content of a note, optionally with specific blocks/sections extracted.
Inputs: note_path (required), include_blocks.
get_similar_notesB
Find notes semantically similar to a given note using embeddings. Returns paths, similarity scores, and available blocks.
Inputs: note_path (required), limit, threshold.
get_statsA
Get statistics about the Smart Connections knowledge base (total notes, blocks, embedding model, etc.).
Inputs: no named parameters.
resolve_linkA
Turn a wikilink into a real file path, the way Obsidian would. Accepts bare text ("Throughline"), full link syntax ("[[Throughline|the CRM tracker]]"), or a path, and honors aliases: frontmatter, so a tracker filed as 2026-06-23-throughline-workstream.md resolves from its codename. Use this whenever you read a [[link]] in a note and need the actual file, instead of guessing at the filename or falling back to semantic search, which finds notes that are SIMILAR rather than the one that was actually referenced. Returns null when nothing resolves, which means the note genuinely does not exist in this vault.
Inputs: link (required).
search_notesA
Semantic search over the vault. Returns an envelope, not a bare array: mode names the engine that answered ("semantic" is real, "keyword" means the embedding model failed to load and results will miss anything phrased differently), coverage says how many notes were actually searched out of the vault total, results holds the matches, and warning appears whenever the answer should not be read at face value. An empty results with mode "semantic" and full coverage means the vault really has nothing closer; an empty results with mode "keyword" or nonzero coverage.unsearchable means the tool was partly blind and you must not report it as an absence. Typical relevant matches score ~0.4-0.75; lower the threshold to widen recall.
Inputs: query (required), limit, threshold.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 10 tools
Most tools are clearly distinct by resource and action, but get_similar_notes, search_notes, and get_embedding_neighbors all touch semantic retrieval and could cause misselection. The descriptions do a good job separating note-based, query-based, and vector-based retrieval, so only one or two tools are genuinely confusable.
Every tool follows a consistent snake_case verb_noun pattern: get_* for retrieval, search_notes for querying, resolve_link for resolution, and check_* for diagnostics. The naming is predictable and makes the toolset easy to navigate.
Ten tools is well-scoped for a read-only vault intelligence server. Each tool earns its place by covering a distinct retrieval, linking, analysis, or health-check function without unnecessary duplication.
The toolset covers the core domain well: semantic search, similar notes, backlinks, connection graphs, note content, wikilink resolution, and retrieval health. Minor gaps exist around explicit vault browsing/list-all-notes or index rebuilding, but agents can complete normal workflows without dead ends.
Maintenance
Related MCP Connectors
Search your Obsidian vault to quickly find notes by title or keyword, summarize related content, aβ¦
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analyβ¦
Token-efficient MCP memory for Markdown vaults. Tiered search, GraphRAG, AI memories.
Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables semantic search and knowledge graph exploration of Obsidian vaults using Smart Connections embeddings. Provides intelligent note discovery, similarity search, and connection mapping through natural language queries.89 npm59MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to perform semantic search across your Obsidian vault using Smart Connections vector database. Provides meaning-based search, related note discovery, and context retrieval for RAG queries instead of basic keyword matching.11-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to find semantic connections and perform text searches in Obsidian vaults using the Smart Connections plugin data.53 npm14MIT
- AlicenseNot gradedqualityBmaintenanceEnables semantic search and retrieval over an Obsidian vault using local or API-based embeddings, allowing AI assistants to find notes by meaning, get related content, and pull context during conversations.16MIT