Connectors
Obsilo can connect to external tools, expose your vault to other AI applications, and let you reach it remotely. It does this through the Model Context Protocol (MCP) and a Cloudflare relay.
MCP client: connect external tools
The MCP client lets Obsilo use tools that live in external MCP servers. You can extend what the agent can do without writing a plugin.
What you can connect
Any MCP-compatible server works. A few common examples:
- Database tools (query SQLite, PostgreSQL, or other databases)
- Web services (call APIs, fetch data)
- Local tools (file system utilities, shell commands, custom scripts)
- Third-party integrations (GitHub, Slack, calendar services)
Setup
- Open Settings > Obsilo Agent > MCP
- Click "+ Add Server"
- Choose the transport type:
| Transport | When to use |
|---|---|
| stdio | Local servers running as command-line processes |
| SSE | Remote servers using Server-Sent Events (legacy) |
| Streamable HTTP | Modern remote servers (recommended for remote) |
- Enter the server command or URL
- Save. The agent picks up available tools automatically.
Once connected, the agent calls external tools with use_mcp_tool and manages servers with manage_mcp_server.
Discovery is automatic
You don't need to tell the agent which tools are available. It reads the tool list from each connected MCP server and uses them when they fit your request.
MCP server: expose your vault to Claude Desktop
You can turn Obsilo into an MCP server so Claude Desktop (or any MCP client) can read and write your Obsidian vault.
Why this matters
Claude Desktop cannot access your Obsidian notes on its own. With Obsilo's MCP server enabled, it gets structured access to your vault: searching, reading, and writing notes through a controlled interface.
Available tools (3 tiers)
| Tier | Tools | What they do |
|---|---|---|
| Read | read_notes, search_vault, get_context | Search and read vault content |
| Session | sync_session, update_memory | Synchronize conversation context and memory |
| Write | write_vault, execute_vault_op | Create and modify notes; run vault operations |
execute_vault_op is the gateway to all vault operations. It lists about 33 available tools at runtime, including vault_health_check, semantic_search, create_pptx, and others. The list is generated from the plugin's tool registry, so new tools show up automatically without any config changes.
Setup
- Open Settings > Obsilo Agent > MCP > Server tab
- Enable the MCP server
- Click "Configure Claude Desktop". This adds the configuration to Claude Desktop's config file for you.
- Restart Claude Desktop
That's it. Claude Desktop now sees your vault as an available tool source.
Write access
The write tier lets Claude Desktop modify your vault. Enable it only if you trust the prompts you send through Claude Desktop. The read and session tiers are safe for everyday use.
Remote access via Cloudflare relay
Remote access lets you talk to your vault from anywhere, as long as Obsidian is running on your machine.
How it works
A Cloudflare Workers relay acts as a bridge between your local Obsilo instance and remote clients. The RelayClient in Obsilo holds a persistent connection to the deployed worker.
Setup
- Deploy the Cloudflare Worker (see the relay deployment guide)
- In Settings > Obsilo Agent > MCP > Remote, enter your worker URL
- Authenticate with the provided token
- The relay connects automatically when Obsidian is running
Always-on requirement
Remote access requires Obsidian to be running on your machine. The relay forwards requests to your local instance. It does not store your vault data in the cloud.
Provider overview
Obsilo supports 10+ AI providers. Most use a plain API key. Two of them use a different auth flow:
| Provider | Auth method | Notes |
|---|---|---|
| GitHub Copilot | OAuth device flow | Uses your existing GitHub Copilot subscription. No separate API key needed. You sign in with your GitHub account. |
| Kilo Gateway | Device auth + manual token | Community gateway with shared rate limits. Device authentication or paste a token manually. |
| Anthropic, OpenAI, Google, etc. | API key | Paste your key in Settings > Models. |
Setting up GitHub Copilot
- Open Settings > Obsilo Agent > Models > + Add Model
- Select GitHub Copilot as the provider
- Click "Sign in with GitHub". A device code appears.
- Open the GitHub URL, enter the code, and authorize
- Select a model (Claude or GPT via Copilot)
Setting up Kilo Gateway
- Select Kilo Gateway as the provider
- Choose Device Auth (recommended) or Manual Token
- For device auth: follow the on-screen flow to authenticate
- For manual token: paste your token from the Kilo dashboard
Free access
GitHub Copilot works if you already have a Copilot subscription. Kilo Gateway offers community access with shared limits. Both are good ways to try Obsilo without buying a separate API key.
Next steps
- Skills, Rules & Workflows: Customize the agent's behavior
- Office Documents: Create presentations and documents
- Multi-Agent & Tasks: Hand work off to sub-agents