Gosidian

MCP文档知识

提供方 未标注

文档知识 HTTP · 远程 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

一个自带内置MCP服务器的独立Markdown知识库。人类通过网页界面编辑,代理通过MCP与之交互,所有内容均以纯.md文件形式存储。

一句话选型结论

按资料字段整理

Gosidian 属于文档知识类 MCP 服务器,HTTP · 远程,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式HTTP · 远程 鉴权未标注 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

HTTP · 远程 未标注
连远程 HTTPS 端点,通常为 Streamable HTTP
docker run -d --name gosidian \ -p 8080:8080 \ -v "$(pwd)/vault:/vault" \ ghcr.io/daniele-chiappa/gosidian:latest # open http://localhost:8080, create admin, copy the MCP token from /admin/tokens claude mcp add gosidian http://localhost:8080/mcp \ --transport http --header "Authorization: Bearer $TOKEN"

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Gosidian当前 未标注 HTTP · 远程 远程部署 有 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

12.6 KB
来自项目仓库与上游目录的原文,未做删改

gosidian

> Markdown notes your AI agents can read, write, and reason over — via MCP.

A self-contained markdown vault with a built-in MCP server. Humans
edit through a web UI, agents talk to it over MCP, everything lives
in plain .md files that Obsidian (and every other markdown tool)
reads natively.

Listed on the official MCP Registry
as io.github.daniele-chiappa/gosidian,
Glama and
mcpservers.org

Try it in your browser

Launch a free, throwaway gosidian in
GitHub Codespaces — no install,
running on your own Codespaces quota. It builds from source, seeds a small
demo vault, and opens the web UI. Log in with demo /
gosidian-demo.

Quick start```bash

docker run -d --name gosidian \
-p 8080:8080 \
-v "$(pwd)/vault:/vault" \
ghcr.io/daniele-chiappa/gosidian:latest

open http://localhost:8080, create admin, copy the MCP token from /admin/tokens

claude mcp add gosidian http://localhost:8080/mcp \
--transport http --header "Authorization: Bearer $TOKEN"
```

Three commands: Docker up → token created from the web UI → agent
wired. Your .md vault is persisted under ./vault/; stop the
container and the files are still there.

Other installation paths (source, custom compose, bare-metal):
docs/getting-started.md.

What is gosidian

  • A markdown vault. Notes are .md files on disk. Open the same
    folder in Obsidian, VS Code, vim, or any editor you already use.
    Zero lock-in: delete .gosidian/ and you have a pure Obsidian
    vault.
  • An MCP server. 71 typed tools let agents bootstrap a session, ingest files,
    search, read, write, link, handoff, self-check, audit. Bearer tokens
    and OAuth grants, each narrowed on every request to what its account
    may read and write.
  • A web UI. A Vue 3 single-page app served from the same binary
    (built with Vite, embedded via go:embed). Notes, graph, search and
    config forms open as windows in a tiling "plancia" workspace —
    full-text search, backlinks, graph view, editor with live preview,
    audit trail, admin pages for tokens and users.

All three views hit the same files on disk. The SQLite FTS5 index
is a cache — drop it and it rebuilds.

Who it's for

  • AI engineers wiring agents that need persistent structured
    memory: note-taking, plans, skills, ADRs, handoffs, audit.
  • Obsidian users who want a programmable layer on top of a vault
    they already trust.
  • Teams sharing one vault: per-project visibility and grants to
    accounts and teams, restricted new accounts with their own project,
    self-service tokens per agent that never outrun their owner.

Why gosidian instead of X

  • vs RAG / vector search: gosidian retrieves the agents' memory by
    identity (path, tag, frontmatter, backlinks) — more predictable
    than similarity search for an agent's working memory. Semantic search
    over the notes is deliberately deferred: see
    ADR-007 rationale. A RAG
    over a project's documents (manuals, reports, scans) is another
    matter, and an experimental
    part of gosidian.
  • vs Obsidian Sync: Sync mirrors a vault between human devices.
    gosidian adds a typed automation surface (MCP) to the same vault.
    Not competitive — complementary.
  • vs Notion / Roam: hosted or proprietary formats; migration is
    a project. gosidian's vault is already .md files you can take
    anywhere.

FAQ covers the long form.

Compared to similar projects

The "markdown vault + agents" space is crowded. This is where gosidian
sits and where it doesn't, as of September 2026:

If you are looking at… What those projects do Where gosidian differs
Obsidian MCP bridges — mcp-obsidian, obsidian-local-rest-api, wrappers around the Obsidian CLI Expose a running Obsidian desktop app to agents over MCP. Headless server: no Obsidian process needed, runs on a box or in a container, multi-user with roles, per-project visibility and grants (accounts and teams), tokens narrowed to each account, audit trail. The vault stays a plain Obsidian vault.
Markdown memory servers — basic-memory, mcp-vault Same "files, not a database" idea; usually add hybrid semantic search, a cloud tier or WebDAV sync. Ships a full web UI, real multi-user, an agent handoff bus and a server-served working method (versioned directives, lint, stale detection). No semantic search by design (ADR-007), no hosted tier.
Client-side wiki skills — obsidian-wiki and the "LLM Wiki" pattern Slash-commands the agent runs locally to compile and maintain a wiki. No server, no auth, no UI. The same pattern implemented server-side and agent-agnostic: one-call scaffold, directives served at bootstrap, handoffs, audit. Complementary: those skills work against a gosidian vault too.
Agent memory services — mem0, agentmemory, mcp-memory-service Memory as an opaque store: embeddings, recall benchmarks, auto-capture hooks. Memory is markdown that humans read in Obsidian or the web UI, retrieved by identity and graph, with no embeddings; a language model is called only by the pipelines you turn on. Auto-capture through Claude Code hooks (contrib/claude-code/: focus injected at session start, session digests at compaction and end) rather than inside the binary. No published recall numbers yet.
Note apps with community MCP servers — SilverBullet, Trilium, SiYuan Mature editors, mobile apps, sometimes real-time collaboration; MCP added by third-party servers on top of their API. MCP-first: the server is in the binary, behind the same login, roles and audit as the UI. No mobile app, no real-time collaboration, no WYSIWYG editor.

Honest gaps, in the order they come up: semantic / hybrid search over
the notes (deferred, see the FAQ;
documents have an experimental RAG),
mobile sync beyond git, real-time collaboration, a hosted offering. The
roadmap says which of these are planned.

Feature highlights

  • Single binary, ≤50 MB, Alpine-based Docker image
  • Web UI: a Vue 3 SPA (Vite, Pinia, Tailwind, CodeMirror, Cytoscape),
    embedded in the binary — editor + live preview, sidebar, search,
    graph view, attachments, audit log, admin pages
  • Plancia tiling window manager (niri-style): notes, graph, search
    and config forms open as resizable, side-by-side windows in a
    horizontally-scrollable workspace, restorable from the URL
  • MCP server over Streamable HTTP (legacy HTTP+SSE kept) with 71 typed tools
  • Bearer tokens with scopes (read / write) and per-project
    restriction — including multi-project tokens for orchestrators;
    every token owned by an account is narrowed on each request to what
    that account may read and write, accounts mint their own (inherit
    follows their access, custom pins a subset), cascade-revoke on
    user disable
  • Agent orchestration bus: handoff notes with an atomic
    claim/complete lifecycle, server-stamped identity, and a
    memory_wait_changes long-poll change feed — a minimal multi-agent
    task queue where everything stays plain markdown
  • Multi-user web login with roles (Admin / User / Read-only) as the
    ceiling, per-project visibility (private / internal / public) for
    reading and grants (read / write / admin) to accounts and
    teams for everything else, delegated to project admins; new
    accounts start restricted with a personal project of their own;
    invite-only signup (24h TTL)
  • Optional TOTP two-factor (global mode + per-user override) and
    LDAP / Active Directory login with guest auto-provisioning
  • Opt-in OAuth 2.1 authorization server so claude.ai / Claude Desktop
    custom connectors, ChatGPT connectors and Claude Code's browser login
    get their own tokens through a consent screen — no pasted bearer
  • Claude Code hooks (contrib/claude-code/):
    the project's hot.md focus injected at every session start, a
    digest of the session appended to the vault at compaction and at the
    end — no LLM, over POST /mcp/append, never blocking the session
  • Optional git sync (debounced commits, push with token auth)
  • SQLite FTS5 full-text search + ETag optimistic locking
  • First-class .html notes, rendered in a sandboxed iframe (off by
    default, opt-in per project)
  • Graph analytics over the wikilink graph: memory_hubs (most-linked
    notes) and memory_path (shortest path between two notes)
  • Opt-in self-improve loop: agents record usage-friction insights
    per token, off by default
  • Print / Save-as-PDF for any markdown note straight from the web UI
  • Internationalization (IT + EN complete; ES / FR / DE scaffolding)
  • Light & dark theme presets (Catppuccin, Tokyo Night, Solarized) +
    custom palette
  • Opinionated Karpathy-Wiki-Stack
    project layout with one-call scaffolding
  • Optional global projects for skills,
    agents & scaffold templates shared across projects (opt-in per
    project, local-overrides-global)

Experimental: pipelines, plugins, RAG and agents

> These parts are new, off by default, and still changing from one
> release to the next: their settings, node types and notes may move,
> and docs/upgrading.md says when they do. The
> core above (the vault, the MCP server, the web UI) does not depend on
> them, and an install that leaves them off sees nothing of them.

  • Pipelines (docs/pipelines.md): a note
    type: pipeline that the server runs when something happens — a file
    arrives, a commit, a chat message, a call from an agent or a service,
    the clock. Its nodes read and write notes, call a language model (any
    OpenAI-compatible endpoint, local or remote), run a script, or wait
    for a person's answer. One queue for all of them, with limits per
    plugin, provider and shared resource (a GPU, say), fair among the
    projects. Edited as text or in a visual editor. They run only once
    [pipelines] enabled = true and a project turns them on.
  • Plugins (docs/plugins.md,
    gosidian-plugins):
    MCP servers beside gosidian, a container each, that add node types to
    the pipelines and tools to the agents. A plugin runs only after the
    owner accepts its manifest, and never sees the vault, only the files
    a pipeline hands it. Published so far:
  • documents: docling (PDF, office files, HTML to markdown), ocr
    (scans, through a vision model), images;
  • data: database (embeddings on PostgreSQL with pgvector, Qdrant or
    SQLite), storage (Nextcloud, S3 or Google Drive as a source of
    files);
  • people: chat (a bot as a widget for any web page), notify
    (Telegram, ntfy, email, with questions to answer);
  • agents and code: claude (Claude Code) and pi (pi.dev) as
    executors, exec (scripts in a sandbox), preview (a static build
    at an address no one guesses).
  • The IN folder (docs/in.md): a project's files to work
    on, under their own names — uploaded from the web UI in resumable
    pieces, sent by an agent, or read from a remote store — which the
    pipelines turn into notes.
  • RAG on a project's documents (docs/chat.md,
    docs/rag-benchmarks.md): the project
    template rag converts the files of the IN folder, cuts the notes into
    paragraphs, stores them with their embeddings, and answers a question
    from them, citing its sources; a bot (type: chat) asks it, on a
    page of its own or a widget on any site. Measured with local models on
    the eight public corpora of ViDoRe V3 (14,514 questions): search
    NDCG@10 52.7 on paragraphs, 57% of the answers judged good, a median
    5.5 s per answer. The agents' own memory stays retrieval by
    identity: the RAG is for documents, not for the vault's notes.
  • Teams of agents (docs/agents.md): a note
    type: team with its roles — a coordinator, writers, developers,
    reviewers — each an agent that a pipeline runs (Claude Code or pi,
    through their plugins), on tasks that are notes of the project.
    gosidian gives the tasks out, checks what each agent changed against
    its role's paths and checks, asks a person before a merge, and counts
    the cost against a budget of the day. A
    pilot runs the same team again and again on
    one objective: training plans for five people and a small web app.
  • Compose presets (docs/deployment.md):
    deploy/presets/ starts gosidian with the RAG chain (docling, images,
    the database plugin on Qdrant, chat) from one .env.

Documentation

Area Start here
Internals Architecture, Development
Common questions FAQ

Full index: docs/README.md.

Contributing

Contributions welcome. See CONTRIBUTING.md for the

Security

Security issues are reported privately. See SECURITY.md
for the disclosure process.

License

Released under the MIT License.

See also

  • PROJECT-STORY.md — project genesis, design
    philosophy, and a comparison with Obsidian / Logseq / RAG-based
    knowledge stacks.
  • CHANGELOG.md — release history.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Gosidian 怎么安装?

在客户端按下面的安装命令接入:docker run -d --name gosidian \ -p 8080:8080 \ -v "$(pwd)/vault:/vault" \ ghcr.io/daniele-chiappa/gosidian:latest # open http://localhost:8080, create admin, copy the MCP token from /admin/tokens claude mcp add gosidian http://localhost:8080/mcp \ --transport http --header "Authorization: Bearer $TOKEN"。装完在客户端配置里引用同一个包或端点。

Gosidian 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Gosidian 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Gosidian 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Gosidian 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Gosidian 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Gosidian 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Gosidian 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。