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, Gemini CLI, 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
• External agent over MCP: use Nexus settings -> Get started -> MCP integration to create connector.js and update Claude Desktop, then see MCP setup guide and Recommended system prompt
• Optional desktop features: Semantic 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.

Feature	Mobile	Desktop
Native chat	Yes	Yes
Workspace memory and tasks	Yes	Yes
MCP clients (Claude Desktop, Cursor, etc.)	No	Yes
Semantic search (local embeddings)	No	Yes
Ingestion (PDF, audio, DOCX)	No	Yes
Composer and Web Tools	No	Yes

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

Use Cases

If you want to...	Start here
Connect Claude Desktop, Codex CLI, Gemini CLI, Cursor, Cline, or another MCP client	MCP setup
Configure built-in chat providers inside Obsidian	Provider setup
Give your agent better instructions for using Nexus	Recommended system prompt
Manage long-running work with persistent workspace context	Workspace memory
Track projects, tasks, blockers, and dependencies	Task management
Search notes and past conversations by meaning	Semantic search
Edit selected text directly in notes	Inline editing
Open webpages in Obsidian and save them as Markdown, PNG, or PDF (experimental)	Apps
Convert PDFs and audio files to Markdown notes — right-click in vault or auto on add (experimental)	Apps
Merge PDFs, concat markdown, or mix audio tracks into one file (experimental)	Apps
Create recurring routines and reusable workflows	Workflow examples
Understand the MCP design and available tools	Two-tool architecture
Extend Nexus with optional apps	Apps

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
• Native chat
• Inline editing
• Apps
• Workflow examples
• Two-tool architecture

Development

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

License

MIT. See LICENSE.