Smart Connections

io.github.gogogadgetbytesPublished by GitHub account gogogadgetbytesv0.2.0Updated Oct 24, 2026

MCP server for Obsidian Smart Connections. Semantic search using your vault's embeddings.

The publisher's own server: Connections

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Lets an assistant semantically search an Obsidian vault's Smart Connections embeddings and read indexed notes.

What you can do
Exposes an Obsidian vault's Smart Connections embeddings for semantic search. Tools include search_by_text (freeform query embedded locally), search_similar (notes similar to a given note), search_by_embedding (raw vector query), get_note (read a note's content), get_model_info, and list_indexed. It is read-only, with path validation against the vault root and bounded responses.
When to use it
Use it when you want an assistant to find and read relevant notes in an Obsidian vault by meaning rather than exact keywords, for example locating notes about a topic or finding notes similar to one you name. It suits read-only retrieval; edits stay in Obsidian.
Requirements
Runs locally as a Node.js 18+ process (npm package @gogogadgetbytes/smart-connections-mcp, stdio). Requires Obsidian with the Smart Connections plugin installed and embeddings already built. The VAULT_PATH environment variable must be set to the absolute path of the vault. First run downloads a roughly 50MB model into the Hugging Face cache. Desktop only.
Before you install
It reads your vault contents, so the assistant can see note text; responses are capped but still leave your machine only as far as your MCP client sends them. It is read-only and exposes no write or shell operations. The first run downloads a model from the network. One vault per server instance.

Installation

In SourceWeft

  1. Open Smart Connections in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Smart Connections MCP Server

[License: MIT] [Node.js Version]

A security-first MCP server for Smart Connections. Read-only. Path-validated. Auditable.

Exposes Smart Connections embeddings to Claude Code and other MCP clients for semantic search of your Obsidian vault.

Why This Exists

We needed semantic search of our Obsidian vault from Claude Code. Existing options have problems:

  • No path validation - User input passed directly to file operations
  • Write access - Some expose mutation tools we don't need
  • Heavy dependencies - PyTorch/transformers for what's essentially vector math

This implementation:

  • Minimal dependencies - MCP SDK + Transformers.js (for text search)
  • Fail-closed security - path validation with realpath, symlink detection
  • Auditable - small TypeScript codebase you can actually read

Features

  • Text search - query with plain text, not just note paths
  • Semantic search using Smart Connections embeddings
  • Local inference - uses Transformers.js (same model as Smart Connections)
  • Read-only - no write operations, no shell execution
  • Secure - strict path validation, bounded responses
  • Offline - works without Obsidian running

Security Model

PropertyGuarantee
Path confinementAll file access validated against vault root
No traversal../ and symlink attacks blocked
Read-onlyNo write operations exposed
Bounded responsesCapped results (50), content length (10KB)
Fail closedErrors deny access, never bypass
Audit loggingSecurity events logged with context

Installation

Prerequisites

  • Node.js 18+
  • Obsidian with Smart Connections plugin installed
  • Embeddings built (open vault in Obsidian, let Smart Connections index)

Setup

bash
git clone https://github.com/gogogadgetbytes/smart-connections-mcpcd smart-connections-mcpnpm installnpm run build

Configure Claude Code

Add to your Claude Code config:

bash
claude mcp add smart-connections \  -e VAULT_PATH="/path/to/your/obsidian/vault" \  -- node /path/to/smart-connections-mcp/dist/index.js

Or manually add to ~/.claude.json:

json
{  "mcpServers": {    "smart-connections": {      "command": "node",      "args": ["/path/to/smart-connections-mcp/dist/index.js"],      "env": {        "VAULT_PATH": "/path/to/your/obsidian/vault"      }    }  }}

Restart Claude Code to load the server.

Usage

Once configured, Claude Code can use these tools:

Search by Text

"Search my vault for notes about backup strategies"→ Uses search_by_text tool

Search Similar Notes

"Find notes similar to Topics/Claude_Code.md"→ Uses search_similar tool

Get Note Content

"Show me the content of Topics/Obsidian.md"→ Uses get_note tool

List Indexed Notes

"What notes are indexed in my vault?"→ Uses list_indexed tool

Tools

ToolDescription
search_by_textSearch using freeform text (computes embedding locally)
search_similarFind notes semantically similar to a given note
search_by_embeddingSearch using a raw embedding vector
get_noteGet content of a specific note (path validated)
get_model_infoGet embedding model configuration
list_indexedList all indexed notes

Configuration

VariableRequiredDescription
VAULT_PATHYesAbsolute path to Obsidian vault

Limitations

  • Single vault - Configure one vault per MCP server instance
  • Index from Smart Connections - Note embeddings come from the plugin; text queries are embedded locally
  • No write access - By design; use Obsidian for edits
  • First run downloads model - ~50MB model cached in ~/.cache/huggingface/

Development

bash
# Buildnpm run build
# Test with MCP Inspectornpx @modelcontextprotocol/inspector node dist/index.js

Contributing

See CONTRIBUTING.md. Security-focused PRs welcome.

Security

To report security vulnerabilities, please email [email protected]. Do not open public issues for security concerns.

License

MIT - see LICENSE

Credits

Source: README.md at commit 24481f8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Connections integrations