M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
C

Claudian

Community
Not a standard server
Bring Claude Code, Codex, and other coding agents into your Obsidian vault

This is not a typical connect-and-use MCP server; read the source repository before using it.

How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #95 of 438
Stars
★ 15.9k Very popular
Transport
stdio (local process) · SSE · Streamable HTTP
Runtime
Node.js · Prebuilt binary
Credentials
API key / credential required
License
MIT
Last commit
62FMRS · C

Claudian is a well-documented, actively maintained (MIT-licensed, sponsored) Obsidian plugin that hosts multiple AI coding-agent CLIs inside a vault; it consumes MCP servers as a client rather than exposing MCP tools itself, so no server-side tool list or install_config applies.

Strongest · Documentation 15/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
13/20
Maintenance
14/20
Documentation
15/20
Setup experience
12/20
Why each score
Reliability 8/20
The README describes chat, inline-edit, slash commands, and MCP connectivity with a fairly detailed source tree, but no server manifest was cached and there is no visible evidence of unit tests, integration tests, or CI workflows. Claimed tool behaviors (file read/write, bash, multi-step workflows) cannot be verified against implementation from static material alone, and error handling/dependency control are undocumented. Per the static calibration rule, absence of executable evidence caps this score low.
Security and permissions 13/20
The Privacy & Data Use section is reasonably transparent: no telemetry, network activity limited to explicit provider/MCP calls, and destinations by provider are disclosed. The architecture lists a core/security (approval utilities) module and a Plan Mode that requires approval before execution, suggesting a confirmation mechanism exists by design. However, this plugin grants AI agents broad file read/write and bash execution over the entire vault, and the README does not specify default permission scope, whether every tool call requires explicit user confirmation, or how credentials for external MCP servers are managed. This is insufficient to confirm least-privilege and full data-flow disclosure, so it cannot score near the top, though nothing in the material indicates a red-line issue (hardcoded secrets, covert exfiltration, or unconfirmed destructive defaults).
Maintenance 14/20
The repo is not archived, uses the MIT license, and has a dedicated CONTRIBUTING.md with explicit PR standards (must explain the problem, solution, rationale, and validation; new-provider PRs are explicitly rejected), indicating clear governance boundaries. Release and community-plugin download badges suggest an ongoing release cadence, and sponsorship (Ke Holdings/BEIKE) implies resourced long-term maintenance. However, no changelog, security-response channel, or dependency-update policy is described in the README, and there is no evidence of response time on the 77 open issues.
Documentation 15/20
The README is layered: features, two install paths (community plugin and from-source), environment requirements, a substantial troubleshooting section (CLI-not-found, PATH conflicts, Windows-specific caveats), a privacy/data-flow disclosure, and an architecture tree. This covers install, dependency troubleshooting, and data-boundary concerns well. It lacks concrete tool/interface parameter documentation (e.g., MCP tool input/output schemas), a changelog or versioning history, and quantified cost guidance (only general mention of needing a subscription or API key), leaving hidden assumptions about the reader's CLI/Node familiarity.
Setup experience 12/20
Installing via the Obsidian community plugin marketplace is simple (search, install, enable), and the from-source path gives concrete commands. But actual functionality depends on a separately installed external CLI (Claude Code/Codex/Grok/OpenCode/Pi) being discoverable by a GUI app, and the README's extensive troubleshooting (spawn ENOENT, nvm/fnm conflicts, Windows .cmd/.exe distinctions, PATH vs. Node.js path mismatches) itself demonstrates this process is fragile and requires manual intervention. No automated verification (CI, tested example configs) demonstrates these steps are reproducible across platforms, and the static calibration rule caps the score accordingly.

Static review · not runListed 2026-08-06

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the network

Best for

  • Obsidian users who want an AI coding-agent chat and inline editor built into their vault
  • Developers already using Claude Code, Codex, or similar CLIs who want vault-aware access to them
  • Note-takers who want agent-assisted file read/write, search, and multi-step workflows scoped to their vault

Not for

  • Users looking for a standalone MCP server to add tools/resources to an MCP client — Claudian is a client/host, not an MCP server
  • Mobile Obsidian users — the plugin is desktop only (macOS, Linux, Windows)
  • Users without any supported CLI harness (Claude Code, Codex, Grok Build, OpenCode, or Pi) installed and a compatible API/subscription provider

Required permissions

  • Read/write/edit access to files within the Obsidian vault (the agent's working directory)
  • Bash/shell command execution via the underlying CLI harness
  • Network access to the selected AI provider (Anthropic, OpenAI, xAI, or OpenCode/Pi providers) and to any configured MCP server endpoints

Risks and side effects

  • Broad file read/write and bash access to the vault means a misbehaving or misprompted agent could modify or delete notes
  • Input, attached files, images, and tool outputs are sent to the selected third-party API provider, so sensitive vault content could leave the local machine
  • MCP servers configured within the plugin are additional third-party endpoints whose trustworthiness is outside Claudian's control

Setup

Before you start

Runtime：Node.js · Prebuilt binary

Recommended: in Obsidian, go to Settings → Community plugins → Browse, search for "Claudian", install, then enable it; or install directly from the community plugin page. From source: clone the repo into the vault's .obsidian/plugins folder, run npm install and npm run build, then enable "Claudian" in Settings → Community plugins.

Check that it works

After installing and enabling the plugin in Obsidian, open the Claudian chat sidebar from the ribbon icon or command palette; if a harness such as Claude Code or Codex loads and the agent can read and write files in your vault, the installation works.

Troubleshooting

  1. If the CLI isn't auto-detected, leave the CLI path setting empty first, then manually set Settings → Advanced → CLI path using `which claude` (macOS/Linux) or `where.exe claude` (Windows)
  2. On Windows, avoid `.cmd`/`.ps1` wrappers — use the native `.exe` for native installs, or `cli-wrapper.cjs` for npm installs
  3. If an npm-installed CLI and Node.js live in different directories, GUI apps like Obsidian may not find Node — add the Node bin directory to PATH in Settings → Environment, or install a native binary instead
  4. Confirm Obsidian is v1.7.2+ and running on desktop (macOS, Linux, Windows), since Claudian is desktop-only

Things to try

Once connected, you can ask your AI assistant things like:

  • Summarize all notes in my vault related to project planning
  • Rewrite the selected paragraph in the current note to be more concise and show a word-level diff preview
  • Search the vault for all files that mention quarterly goals and list their paths
  • Compile a list of unfinished tasks from across my vault

Use cases

Chat with Claude Code, Codex, Grok Build, OpenCode, or Pi directly inside Obsidian notes
Inline-edit note text with word-level diff preview via an AI agent
Use vault files, subagents, and MCP servers as @mentions in agent conversations
Manage multiple agent chat sessions across tabs or a dual-pane session manager

Overview

Claudian is an open-source (MIT-licensed) Obsidian plugin that embeds AI coding agents — Claude Code, Codex, Grok Build, OpenCode, and Pi — as collaborators inside an Obsidian vault. It turns the vault into the agent's working directory, enabling file read/write, search, bash execution, and multi-step workflows via a chat sidebar, inline text editing, slash commands, and @mentions. Claudian itself is not an MCP server; it functions as an MCP-capable client, letting the Claude Code harness connect to external MCP servers over stdio, SSE, or HTTP from within Obsidian.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 64.1k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision c70aef044349 Data synced 2026-11-04 Read the FMRS scoring method