Skip to main content
Glama
dweigend

Joplin MCP Server

by dweigend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JOPLIN_TOKENYesThe Joplin API token obtained from Joplin Desktop (Tools -> Options -> Web Clipper). Required for accessing the Joplin API.
MCP_LOG_LEVELNoOptional log level for debugging (e.g., 'debug'). If not set, the server uses default logging.

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search_notesC

Search for notes in Joplin.

Args:
    args: Search parameters
        query: Search query string
        limit: Maximum number of results (default: 100)

Returns:
    Dictionary containing search results
get_noteC

Get a specific note by ID.

Args:
    note_id: ID of the note to retrieve

Returns:
    Dictionary containing the note data
create_noteA

Create a new note in Joplin.

Args:
    args: Note creation parameters
        title: Note title
        body: Note content in Markdown (optional)
        parent_id: ID of parent folder (optional)
        is_todo: Whether this is a todo item (optional)

Returns:
    Dictionary containing the created note data
update_noteB

Update an existing note in Joplin.

Args:
    args: Note update parameters
        note_id: ID of note to update
        title: New title (optional)
        body: New content (optional)
        parent_id: New parent folder ID (optional)
        is_todo: New todo status (optional)

Returns:
    Dictionary containing the updated note data
delete_noteB

Delete a note from Joplin.

Args:
    note_id: ID of note to delete
    permanent: If True, permanently delete the note

Returns:
    Dictionary containing the operation status
import_markdownC

Import a markdown file as a new note.

Args:
    args: Import parameters
        file_path: Path to the markdown file

Returns:
    Dictionary containing the created note data

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

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: create_note, delete_note, get_note, update_note, search_notes, and import_markdown all target specific operations on notes. An agent can easily distinguish between creation, retrieval, modification, deletion, searching, and importing functions without confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case naming: create_note, delete_note, get_note, update_note, search_notes, and import_markdown. The pattern is predictable throughout, making the tool set easy to navigate and understand.

Tool Count5/5

With 6 tools, the server is well-scoped for note management in Joplin. Each tool earns its place by covering essential CRUD operations (create, read, update, delete), plus useful extras like search and import, without being overly sparse or bloated.

Completeness5/5

The tool set provides complete CRUD and lifecycle coverage for notes in Joplin, including create, read, update, delete, search, and import functionalities. There are no obvious gaps, and agents can perform all core note-related workflows without dead ends.

Maintenance

ActivitySlowing
ResponsivenessUnresponsive

Resources