Skip to main content
Glama
belsar-ai

joplin-mcp

by belsar-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to joplin-mcp

No user-submitted related servers found.

    Related Servers

    • Joplin MCP Server

      dweigend
      A
      license
      A
      quality
      D
      maintenance
      A server that enables AI assistants to access and manipulate Joplin notes through the Model Context Protocol, allowing search, reading, editing, and management of notes using natural language.
      6
      90
      MIT

    • joplin-mcp

      biontdv
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that turns your Joplin notebook into a tool an LLM can actually use — read, search, write, and organize notes, and pull OCR'd text straight out of your screenshots.
      13
      1
      MIT

    • Agentic-Joplin MCP Server

      sohampatwardhan
      A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol server that wraps Joplin's Data API, giving agents full CRUD over notes, notebooks, tags, and resources, plus search and revision history.
      MIT

    • Joplin MCP Server

      Darkflib
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides standardized tools for querying and retrieving notes from Joplin personal knowledge manager through its API, enabling AI assistants to access and reference personal notes contextually.
      9
      MIT

    • joplin-mcp

      johnsarie27
      A
      license
      A
      quality
      A
      maintenance
      A minimal MCP server that enables interaction with Joplin notes and notebooks through the local Web Clipper REST API, providing tools for search, create, update, and note management.
      13
      MIT
    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.6/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have nearly identical names and both execute JavaScript, differing only in permissions (read-only vs. write). The descriptions are detailed enough to distinguish them, but the overlap in core functionality could cause initial confusion for an agent.

    Naming Consistency5/5

    Both tool names follow a consistent 'execute_joplin_<permission>_script' pattern, using snake_case and clear permission labels (readonly vs. script). No mixing of conventions.

    Tool Count3/5

    Only 2 tools for a server that exposes a full API (CRUD for notebooks, notes, search, etc.) feels minimal. While the design intentionally wraps everything into two script executors, a more granular tool surface might be expected given the scope.

    Completeness5/5

    All operations available through the Joplin API are accessible via the two tools (read-only in one, write in the other). No obvious gaps in functionality; the set fully covers the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources