Joplin MCP Server
Connect a local Joplin vault to your agent so it can read, tag, and import notes while you build docs and runbooks alongside code.
Overview
Joplin MCP Server is a MCP server for the Build phase that exposes Joplin notes, notebooks, tags, and imports to agents over stdio via the Web Clipper API.
What is this MCP server?
- FastMCP stdio server exposing Joplin notes, notebooks, tags, and imports
- PyPI package joplin-mcp at version 0.8.0
- Authenticates via Joplin Web Clipper token against a running Joplin instance
- Optional JOPLIN_URL override (default http://localhost:41184)
- Self-hosted notes—data stays on your machine unless you sync Joplin yourself
- Package version 0.8.0
- 2 documented environment variables (JOPLIN_TOKEN required, JOPLIN_URL optional)
- Default Joplin Web Clipper base URL http://localhost:41184
Community signal: 129 GitHub stars.
What problem does it solve?
Your specs and runbooks live in Joplin but your agent cannot see them without copy-paste and stale context every session.
Who is it for?
Solo builders who standardize on self-hosted Joplin and want MCP stdio integration from PyPI without building a custom REST wrapper.
Skip if: Teams on Notion-only stacks, cloud-only PKM with no Joplin, or environments where localhost clipper access is blocked.
What do I get? / Deliverables
Your agent queries and updates Joplin-backed notes through MCP while you implement features and documentation in one workflow.
- MCP tools for listing and manipulating Joplin notes, notebooks, and tags
- Import pathways exposed to the agent per server capabilities
- Single-vault context for build-time specs without manual paste
Recommended MCP Servers
Journey fit
Note and knowledge-base wiring is build-phase agent tooling that keeps specs, snippets, and ship checklists in sync with implementation. Agent-tooling subphase is where MCP bridges external productivity apps into the coding session.
How it compares
Local notes MCP bridge, not a hosted markdown CMS or a generic browser automation skill.
Common Questions / FAQ
Who is Joplin MCP Server for?
It is for developers who run Joplin locally or on a reachable instance and want their AI coding agent to use that vault as structured context.
When should I use Joplin MCP Server?
Use it during build and docs work when notebooks should stay authoritative while the agent edits code and references the same notes.
How do I add Joplin MCP Server to my agent?
Install the joplin-mcp PyPI package, set JOPLIN_TOKEN from Joplin’s Web Clipper settings, optionally set JOPLIN_URL, and register the stdio server in your MCP client config.