obsidian-bridge
Connects Codex and compatible ChatGPT desktop plugin hosts to local Obsidian vaults for search, reading, and optional note creation/appending.
README
Obsidian Bridge
Obsidian Bridge connects Codex and compatible ChatGPT desktop plugin hosts to local Obsidian vaults. It can search and read notes and, only when you enable it, create a note or append text. Vault and folder permissions are managed from the Bridge Control panel inside Obsidian.
[!WARNING] This is an independent public preview, not an official Obsidian or OpenAI product. Start with a disposable vault or test folder and keep an independent backup.
[!IMPORTANT] Content returned by the bridge reaches the MCP host and may be sent to the model answering your request. The bridge itself has no network client, telemetry, account system, or remote index. Read PRIVACY.md before authorizing sensitive notes.
What it provides
- A guided Windows installer with vault discovery and no administrator privileges.
- A visual Obsidian settings panel for separate read and write folder selection.
- Eight bounded, non-mutating read tools for search, excerpts, outlines, links, tags, backlinks, and recent notes.
- A separate writer process limited to create and append.
- A two-step write protocol: preview first, then an explicit confirmation and commit.
- Default-deny access, per-vault settings, hidden-folder rejection, path containment, timeouts, and output limits.
- Local recovery backups for append and content-free write audit metadata.
Quick start on Windows
- Download Obsidian-Bridge-Setup-0.3.3.zip from the latest release.
- Extract the ZIP completely. Do not run the installer from inside the archive preview.
- Double-click INSTALLA-OBSIDIAN-BRIDGE.cmd.
- Select a vault and complete the guided installation.
- In Obsidian, open Settings → Community plugins → Bridge Control.
- Select Choose folders, enable Read and optionally Write, then save access.
- Start a new Codex task and test a synthetic note.
The installer keeps new vaults deny-by-default and preserves existing Bridge Control permissions during an update. The full walkthrough is in docs/INSTALLATION.en.md.
Use the asset whose name starts with Obsidian-Bridge-Setup. GitHub's automatically generated Source code archives are development snapshots, not the guided installer. SHA-256 values are published beside every release in SHA256-0.3.3.txt.
The 0.3.3 installer and Bridge Control interface are currently in Italian; the English guide maps each step.
If diagnostics report that the Obsidian CLI is unavailable, enable it under Obsidian → Settings → General → Command line interface. The bridge uses the official local CLI and does not emulate vault access through an HTTP service.
Install through the Codex marketplace
Advanced users can add this public repository as a Codex marketplace:
codex plugin marketplace add studentepercaso/obsidian-bridge --ref 0.3.3
codex plugin add obsidian-bridge@obsidian-bridge-community
The marketplace installs the Codex plugin component. The release installer remains the recommended route because it also installs Bridge Control in the selected vault and creates the shared local configuration.
Permission and write model
Reading can be disabled, limited to selected folders, or extended to the eligible vault. Writing has a separate switch and separate folder list and is disabled by default.
Every write uses two calls:
- Prepare validates the vault, path, permission, source state, and proposed content. It returns a bounded preview without changing the note.
- Commit accepts only that unexpired, single-use preview after explicit confirmation and rechecks permissions and source state.
The writer cannot delete, rename, move, overwrite arbitrary files, execute shell commands, manage plugins, or invoke arbitrary Obsidian commands. Read and write tools run in separate MCP processes with different approval policies.
Requirements
- Windows 10 or 11 for the guided installer in this preview.
- Obsidian desktop 1.12.7 or newer.
- The official Obsidian CLI enabled when requested by diagnostics.
- Node.js 20 or newer.
- Codex/ChatGPT desktop with local plugin support, or a compatible local MCP host that supports stdio and approval for mutating tools.
Obsidian must run in an interactive desktop session. This release does not directly connect to the ChatGPT website.
Development and verification
npm ci
npm --prefix companion/obsidian-bridge-control ci
npm run check:all
Automated tests use a simulated CLI and synthetic data. A release also requires a manual smoke test with the official Obsidian CLI and a disposable vault. See docs/SUBMISSION_TESTS.md.
Documentation
- English installation guide
- Guida di installazione in italiano
- Controlled writing protocol
- Privacy
- Security policy
- Changelog
- Contributing
- Support
- Third-party notices
Project status
Version 0.3.3 is a public community preview distributed from GitHub. The Bridge Control companion is also published in its own review-ready repository for submission to the official Obsidian Community Plugins directory. The local stdio MCP architecture is not the same as a hosted MCP endpoint and is not currently submitted to the universal OpenAI Plugins Directory.
Obsidian is a trademark of Dynalist Inc. ChatGPT, Codex, and OpenAI are trademarks of OpenAI. This independent project is not affiliated with or endorsed by either company.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.