fenced-obsidian-sync-mcp
Provides finely fenced access to an Obsidian vault, allowing agents to list, read, create, update, delete, move, and search notes with path-scoped permissions.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fenced-obsidian-sync-mcpcreate a note in my inbox titled 'Meeting Notes'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
fenced-obsidian-sync-mcp
A deny-by-default, finely fenced MCP server
over an Obsidian vault. The operator declares exactly which capabilities (list,
read, create, …) an agent gets, each scoped by path globs — and everything
else is impossible by construction, not merely guarded.
Other Obsidian MCP servers hand an agent broad read/write/search/delete. Here
the fence is the product: you can run it so an agent may only create notes
under Inbox/, or only see note titles, or touch nothing at all — and prove
the rest is impossible because the tools are never registered.
Full design brief:
docs/SPEC.md. The "Core principles (security invariants)" there are requirements, and each is backed by a test.
Install
pip install -e ".[http,dev]" # http extra for remote serving; dev for testsRequires Python ≥ 3.10.
Related MCP server: kObsidian MCP
Run
fenced-obsidian-sync-mcp --config examples/create-only.yaml
# or
python -m fenced_obsidian_sync_mcp --config examples/create-only.yamlBy default this speaks stdio (for a local MCP client). Set
transport.type: http for remote serving (see below).
The three canonical postures
Each is a complete, runnable config (full files in examples/).
1. Deny-all — a dark vault
The server runs but exposes no tools at all.
mode: local
vault: /path/to/your/vault
capabilities: {}2. Create-only — file, never read
The agent can drop new notes into Inbox/ and do nothing else. No
read/list/update/delete tool is registered. Collisions never overwrite.
mode: local
vault: /path/to/your/vault
collision: suffix # fail | suffix
capabilities:
create:
enabled: true
allow: ["Inbox/**"]3. Titles-only — see names, not bodies
The agent learns which notes exist (to suggest links) but no registered tool
can open their contents. read and read_metadata are absent.
mode: local
vault: /path/to/your/vault
capabilities:
list:
enabled: true
allow: ["**/*.md"]
deny: ["Private/**", "Journal/**"]Capabilities
Every capability is off by default and independently path-scoped. Enabling one registers exactly one tool; disabling it means the tool is absent from the MCP tool list.
Capability | Tool | Exposes | Opens file contents? |
|
| enumerate paths / filenames | no — |
|
| frontmatter, tags, stat | frontmatter only |
|
| full note contents | yes |
|
| content search (implies | yes |
|
| new files only, never overwrite | no |
|
| modify / append existing files | n/a |
|
| remove files | n/a |
|
| rename / relocate, never overwrite | n/a |
search implies read: enabling search without read is a config error,
because returning snippets while read is off would be a content oracle.
Glob semantics
Globs use wcmatch with GLOBSTAR,
evaluated against vault-relative POSIX paths:
**spans directories (**/*.mdmatches at any depth);*matches within a single segment.Case-sensitive.
Dotfiles are not matched unless a pattern names the leading dot, so
.obsidian/stays out of**/*.md.denyalways beatsallowon every capability.
Modes
mode: local— pointvaultat a directory you already keep current (Syncthing, iCloud, git, or nothing). No sync subprocess, noobsidian-headlessdependency. Works anywhere, including a phone via Termux.mode: sync—vaultis your remote Obsidian Sync vault name andvault_diris the local directory the officialobsidian-headlessclient (ob sync --continuous) mirrors into. The server supervises that process.
The fence is identical in both modes; only how the directory stays current differs.
⚠️ Sync-mode write warning: in
syncmode,update/delete/movepropagate to every device on your Obsidian Sync. Create-only is the conflict-free default; enable writes deliberately.
Transports
stdio (default) — for a local MCP client.
HTTP (
transport.type: http) — streamable-http behind a bearer token (required) and TLS. Terminate TLS in-process (transport.tls.certfile/keyfile) or at a reverse proxy such as Caddy. Full OAuth is a future extension; bearer + TLS is the supported remote posture today.
transport:
type: http
host: 0.0.0.0
port: 8080
auth: { bearer_token: "a-long-random-secret" }
tls: { certfile: /etc/ssl/certs/server.crt, keyfile: /etc/ssl/private/server.key }Audit log
Optional structured JSONL of every allowed and denied call (capability, path, decision, and — for denials — an internal reason never shown to the client):
audit:
enabled: true
path: /var/log/fenced-obsidian-sync-mcp/audit.jsonl # omit -> stderrDeploy with Docker (mode: sync)
The repo ships a Dockerfile, docker-compose.yml, and Makefile for running
mode: sync behind a reverse proxy (e.g. the central Caddy on a Hetzner box).
The image bundles both the Python server and the official obsidian-headless
(ob) client; TLS is terminated at the proxy, so the container speaks plain
HTTP on 0.0.0.0:4012 and the bearer token comes from $FOSM_BEARER_TOKEN.
# 1. one-time obsidian-headless auth (persists in named volumes)
make ob-login # interactive: email, password, MFA
make ob-setup VAULT="My Vault" # links the remote vault into /vault
# 2. config + secret
cp examples/config.docker-sync.yaml config.yaml # edit vault name + globs
cp .env.example .env && echo "FOSM_BEARER_TOKEN=$(openssl rand -hex 32)" > .env
# 3. run
make deploy # docker compose up -d --buildbearer_token_env: FOSM_BEARER_TOKEN in the config sources the token from the
container environment, keeping the secret out of the config file and git. Point
your reverse proxy at 172.18.0.1:4012 (the Docker bridge gateway) and, because
MCP streamable-http uses SSE, disable proxy buffering — in Caddy:
reverse_proxy 172.18.0.1:4012 { flush_interval -1 }.
Security invariants
These are guaranteed and tested (tests/):
Deny by default — a disabled capability's tool is not registered.
Capabilities are independent — knowing a note exists (
list) is separate from its metadata (read_metadata) is separate from its body (read).Path confinement —
.., absolute paths, escaping symlinks, and percent-/double-encoded separators are all rejected.No silent overwrite —
createusesO_EXCL; collisionsfailorsuffix.Glob-scoped, deny-wins —
denyalways beatsallow.No existence oracle — denied paths return a uniform
not permitted.Auditable — optional structured log; a small, readable codebase.
Development
pip install -e ".[http,dev]"
pytest # full invariant + acceptance suite
ruff check .License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mmsge/fenced-obsidian-sync-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server