Quick Configuration
Choose the setup that matches your environment.
Before You Start
- Confirm you have the account, endpoint, or API key required for Obsidian.
- Start with minimum scopes and read-only access where possible.
- Keep secrets in environment variables instead of hardcoding them in JSON.
This MCP does not have a tested config yet
Do not treat a generic endpoint placeholder as a real setup. Verify the official install path, command/url, env vars, and scopes first; if you already have sanitized config, run it through the checker.
Open config checkerCommon Pitfalls & Fixes
- ⚠️ Watch out: Vault path scope, linking conventions, and avoiding accidental edits.
- 🔑 Always store API keys in environment variables, never hardcode them in JSON.
- 🛡️ Start with read-only scopes if available to verify connection safely.
Example Prompts
Once connected, try these prompts to test capabilities:
- Search my vault for notes about "MCP" and summarize the key takeaways.
- Find all notes tagged #todo and extract a task list grouped by topic.
- Create a draft note "Weekly Review" that links to the 5 most recently edited notes.
Verification Checklist
- Run 1-2 real prompts to confirm Obsidian returns usable data.
- Check that error messages are clear enough for troubleshooting.
- Document the required scopes, dependencies, and env vars for future reuse.