AI: Model Context Protocol (MCP)
Aren’t we living in an incredible time? Every other week another major AI innovation, tool, or protocol drops. This time, we’re taking a look at the Model Context Protocol (MCP).
By now, you should know what Large Language Models (LLMs) are. Claude, GPT, Gemini, etc. They’re great at predicting the next word in a sentence, but not so great at talking to APIs or clicking UI buttons for you. Just like we rely on user interfaces instead of manually editing code to make programs do what we want, LLMs rely on MCP to interact with tools.
Sure, you could let an LLM directly call an API, but the model would need to write code, hold a lot of context, and rely on documentation that’s not always written optimally. MCP solves this by abstracting away the complexity. The LLM simply calls a tool through MCP, and the MCP implementation handles the real work - running code, making API calls, or interacting with local software.
Using MCP with Claude Desktop + Obsidian
Below is a step-by-step guide showing how to configure Claude Desktop with MCP so it can interact with Obsidian and create a note!
1. Configure Docker Desktop for MCP Toolkit
We start by setting up the official MCP Docker Toolkit.
Docker provides an environment where Claude Desktop can connect to the MCP toolkits:
Open Docker desktop → MCP Toolkit (beta) → Clients → "Connect" Claude Desktop

2. Install the Local REST API Plugin for Obsidian
Next, install the Obsidian Local REST API community plugin:
- Open Obsidian → Settings → Community Plugins
- Browse for Local REST API
- Install & enable it
This exposes a localhost REST interface that MCP can talk to via Claude.

3. Install the Obsidian MCP Toolkit
Now install the Obsidian MCP Toolkit, which acts as a bridge between Claude’s MCP layer and the Obsidian REST API.
This toolkit allows Claude to:
- Create files
- Read notes
- Append to notes
- Search vault content
- Etc.
Open Docker desktop → MCP Toolkit (beta) → Catalog → "Add MCP server" Obsidian

4. Configure the Local REST API Key for the Obsidian MCP Toolkit
Inside the Obsidian Local REST API plugin settings, generate an API key.
Copy this key into your Obsidian MCP Toolkit configuration.
Claude will use this key to authenticate requests to Obsidian.


5. Restart Claude Desktop & Verify MCP_DOCKER is Enabled
Close and reopen Claude Desktop to make it detect the new MCP toolchains.
After restarting:
- Open Settings → Connectors
- Check whether MCP_DOCKER is listed

6. Verify the Obsidian Toolkit is Available in Claude Desktop
In the same Configure page for MCP_DOCKER, you should now see the Obsidian MCP Toolkit as an available integration.
Make sure the tools "obsidian_*" are listed as “Needs approval”, or “Always allow”.

7. Write a “Hello world” Note Using the Obsidian Toolkit
Now for the fun part.
Open a new Claude Desktop chat and type something like:
Create a new note in Obsidian called hello world with the content:
"Write me a 'Hello world' note using obsidian"
Claude will detect that the Obsidian Toolkit can perform this action and will offer to use it.

8. Allow Claude Desktop to Use the Obsidian Toolkit
Claude will show a permission popup asking whether it can access the Obsidian MCP tool.
Click Allow.
This authorizes Claude to send the MPC command to Obsidian through your local REST API.


9. Confirm the File Was Created in Obsidian
Open your Obsidian vault.
You should now see:
📄 Hello world.md
Inside you’ll find the content Claude generated.


At this point, everything is wired correctly:
Claude Desktop → MCP → Docker Toolkit → Obsidian MCP Toolkit → Local REST API → Obsidian.
Now go ham. Explore the toolkits! This stuff is ridiculously powerful! For your everyday personal tools or even that API you want to wire up for your next hackathon project!
Enjoyed this post? Subscribe below and get notified when my next exploration drops. I’d love to have you along for the ride! 👇