Nexus MCP for Obsidian

Nexus gives AI agents and built-in chat access to your Obsidian vault so you can read, write, search, organize, and automate notes in natural language while keeping storage local to the vault.

Nexus can be used in two ways:

• Inside Obsidian with native chat (hook up to your favorite provider or agentic platform!)
• From external agents like Claude Desktop, Claude Code, Codex CLI, Antigravity, Cursor, Cline, and other MCP clients

Nexus is the successor to Claudesidian. Legacy installs in .obsidian/plugins/claudesidian-mcp/ still work.

Setup

• Install the latest release from GitHub Releases: manifest.json, styles.css, and main.js
• Put them in .obsidian/plugins/nexus/ and enable Nexus in Obsidian
• Native chat in Obsidian: Provider setup and Native chat guide for chat, live voice, read-aloud, and built-in audio/video generation
• External agent over MCP: use Nexus settings -> Get started -> Connect an external agent to connect Claude Desktop, Claude Code, Codex or Antigravity in one click, or follow its Other agents steps for any other MCP client, then see MCP setup guide and Recommended system prompt
• External agent over CLI (no MCP config): install the nexus command from Get started -> Connect an external agent -> Command line so shell agents (Claude Code, Cursor, Codex) can drive your vault directly — see the Nexus CLI guide. Installation is user-triggered, writes only outside the vault, and on Windows adds the Nexus directory to the current user's PATH without administrator rights; uninstall removes only entries Nexus recorded as its own.
• Optional desktop features: Semantic search, Adaptive search, and Apps and integrations

Native chat works on desktop and mobile. MCP clients, local desktop providers, and semantic search are desktop-only.

Mobile Support (Experimental)

Native chat works on mobile (iOS and Android). Desktop-only features gracefully skip loading on mobile -- they will not appear or cause errors.

Mobile support is new and may have bugs. Please report issues on GitHub.

Network Use

Nexus does not call out on its own. Nothing is sent when the plugin loads unless you have enabled a remote agent (see below), and there is no telemetry, analytics, crash reporting, or usage tracking of any kind. Your notes stay in your vault unless you do something that sends them somewhere. Every request below is listed with the action that causes it.

AI provider APIs. Entering or replacing an API key starts an automatic validation request after you stop typing. Opening a provider's settings asks that provider for its current model list, so models it no longer offers can be marked; OpenRouter's list is public and is fetched without your key. Using a provider then sends your prompt — and whatever vault content the agent decides to include — to that provider. Your key is only ever sent to the provider it belongs to.

Ollama and LM Studio talk to your own machine and leave it entirely.

Addresses you add yourself. An OpenAI-compatible endpoint (Providers) is contacted only at the URL you enter, and only when you connect to discover models or chat with one of its models. A Hermes or OpenClaw remote agent (Remote agents) is contacted only at the URL you enter; while a connection is enabled, Nexus also checks its availability once on startup and every 30 seconds after that, without sending any vault content. A task delegated to a remote agent sends that agent the task text and whatever context the model attaches to it. Turn the connection off to stop all of these requests.

Downloads for optional desktop features. A few features fetch their engine the first time you enable them, rather than shipping inside main.js — the download is cached and does not repeat. Never enabling the feature means never making the request.

Housekeeping. Opening Nexus settings checks for a newer version (api.github.com, raw.githubusercontent.com). Asking an agent to load the built-in guides workspace fetches the current guides (raw.githubusercontent.com).

Not requests. Two things look like external hosts but aren't. Calls to OpenRouter and Requesty carry HTTP-Referer: https://synapticlabs.ai and X-Title: Nexus — the app-attribution headers those routers show in their dashboards. They are header values; nothing is fetched from that address. And buttons like Download Node.js or Get an API key open nodejs.org, ollama.com, lmstudio.ai, claude.ai, github.com, or the provider's own console (platform.openai.com, console.anthropic.com, aistudio.google.com, and so on) in your browser — the plugin never retrieves them.

Use Cases

Prompt For Your Agent

If you want another agent to walk you through setup, paste this:

Help me set up Nexus for Obsidian and guide me step by step.

Use these docs as the source of truth:
- README: https://github.com/ProfSynapse/claudesidian-mcp/blob/main/README.md
- Provider setup: https://github.com/ProfSynapse/claudesidian-mcp/blob/main/guide/provider-setup.md
- MCP setup: https://github.com/ProfSynapse/claudesidian-mcp/blob/main/guide/mcp-setup.md
- Recommended system prompt: https://github.com/ProfSynapse/claudesidian-mcp/blob/main/guide/recommended-system-prompt.md
- Native chat guide: https://github.com/ProfSynapse/claudesidian-mcp/blob/main/guide/native-chat.md

Start by figuring out whether I want native chat inside Obsidian, an external MCP agent, or both. Ask for my OS and the agent I want to use if that matters. Then walk me through the exact setup path, one step at a time.

When a config file needs to be edited, show the exact snippet with my vault path inserted. Do not invent config formats or skip restart/reload steps. If multiple setup paths are possible, recommend the simplest one first.

More Guides

• Workspace memory
• Task management
• Semantic search
• Adaptive search
• Native chat
• Inline editing
• Apps
• Workflow examples
• Two-tool architecture
• Nexus CLI

Development

npm install
npm run dev
npm run build
npm run test
npm run lint

License

MIT. See LICENSE.