Skip to main content
Glama
biontdv

joplin-mcp

by biontdv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JOPLIN_TOKENYesYour Web Clipper authorization token
JOPLIN_BASE_URLNoBase URL of the Joplin Web Clipper APIhttp://127.0.0.1:41184

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_notebooksA

List all Joplin notebooks (folders), with id, title and parent_id.

create_notebookA

Create a new notebook (folder). Use parent_id to nest it under an existing notebook, e.g. a client/project notebook.

Args:
    title: Notebook title.
    parent_id: Parent notebook (folder) id to nest under, if any.
update_notebookA

Rename and/or move a notebook. Only the fields provided are changed.

Args:
    notebook_id: The Joplin notebook (folder) id to edit.
    title: New title, if renaming it.
    parent_id: New parent notebook id, if moving it. Pass an empty string
        to move it to the top level (no parent).
delete_notebookA

Delete a notebook by id, including all notes and sub-notebooks inside it. In Joplin this moves the notebook to the trash (or permanently deletes it if the trash is disabled in the app's settings).

Args:
    notebook_id: The Joplin notebook (folder) id to delete.
list_notesA

List notes, optionally filtered to a single notebook.

Args:
    notebook_id: If set, only return notes inside this notebook (folder id).
    limit: Max notes per page (Joplin caps this at 100).
    page: Page number, starting at 1.
search_notesA

Full-text search notes using Joplin's search syntax (e.g. 'title:foo', 'tag:bar').

Args:
    query: Search query string.
    limit: Max results per page (Joplin caps this at 100).
    page: Page number, starting at 1.
get_noteA

Fetch a single note's full content (including body) by id.

Args:
    note_id: The Joplin note id.
create_noteA

Create a new note.

Args:
    title: Note title.
    body: Note body in Markdown.
    notebook_id: Target notebook (folder) id. If omitted, Joplin uses the
        currently selected notebook in the app.
    is_todo: If true, create the note as a to-do item.
update_noteA

Edit an existing note. Only the fields provided are changed.

Args:
    note_id: The Joplin note id to edit.
    title: New title, if changing it.
    body: New Markdown body, if changing it (replaces the whole body).
    notebook_id: Move the note to this notebook id, if changing it.
    is_todo: Convert to/from a to-do item, if changing it.
    todo_completed: Mark a to-do complete/incomplete, if changing it.
get_resource_infoA

Fetch metadata for a Joplin resource (an attachment/image embedded in a note body, referenced there as ':/'), including its mime type and file extension. Use this before get_resource_file to pick a sensible file extension for the saved file.

Args:
    resource_id: The Joplin resource id.
get_resource_fileA

Download a Joplin resource's raw file (e.g. a screenshot embedded in a note) and save it to a local path, so it can then be viewed with a file-reading tool. Call get_resource_info first if you need the mime type to choose the save_path's extension.

Args:
    resource_id: The Joplin resource id (from a note body link like ':/<id>').
    save_path: Absolute local file path to save the downloaded file to.
get_resource_ocr_textA

Fetch the OCR-extracted text for a Joplin resource (e.g. text recognized inside a screenshot or scanned PDF/image attachment), without downloading the file itself. Requires Joplin's built-in OCR feature to be enabled (Options > General > "Enable document text extraction") and to have finished processing the resource.

The returned `ocr_status` is one of: 0=not queued yet, 1=queued/todo,
2=processing, 3=done, 4=error (see `ocr_error` if it failed). If OCR
hasn't finished yet, retry after a short delay.

Note: Joplin also automatically indexes ocr_text for full-text search,
so search_notes may already surface hits found only inside an image via
OCR without needing this tool.

Args:
    resource_id: The Joplin resource id (from a note body link like ':/<id>').
delete_noteA

Delete a note by id. In Joplin this moves the note to the trash (or permanently deletes it if the trash is disabled in the app's settings).

Args:
    note_id: The Joplin note id to delete.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 13 tools

Disambiguation5/5

Each tool targets a distinct resource and action: notebooks (create/list/update/delete), notes (create/get/list/update/delete/search), and resources (info/file/OCR). There is no overlap in purpose, and descriptions clearly distinguish similar operations like get_note vs list_notes.

Naming Consistency5/5

All tool names follow the same verb_noun pattern in snake_case (e.g., create_notebook, list_notes, get_resource_file). Pluralization is consistent for list operations, and verbs are uniform across resource types.

Tool Count5/5

With 13 tools, the surface is well-scoped for a note-taking domain: full CRUD for notebooks and notes, plus search and resource handling. Each tool serves a clear purpose without unnecessary bloat.

Completeness4/5

The set covers all core note and notebook operations (create, read, update, delete, list, search), and resource retrieval is handled. Minor gaps exist: no single-notebook getter and no resource listing/deletion, but these are non-critical and agents can work around them.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources