Skip to main content
Glama
jamesfishwick

Slipbox MCP Server

by jamesfishwick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Slipbox MCP Server

No user-submitted related servers found.

    Related Servers

    • Librarian MCP Server

      MasterWushi
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that gives AI agents structured access to a personal Obsidian knowledge vault, with semantic search, organization through Maps of Content, and git-backed history.
      -

    • zk-mcp

      koei-kaji
      A
      license
      C
      quality
      F
      maintenance
      An MCP server that integrates the zk note-taking system with LLMs, enabling users to search, read, create, and manage notes. It provides tools for link analysis, tag management, and complex note queries to interact with local knowledge bases.
      5
      1
      MIT

    • vault-master-mcp

      mattbotcode
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that treats Obsidian vaults as knowledge graphs, enabling AI agents to traverse wikilinks, assemble token-budgeted context, and search with backlink awareness.
      3 npm
      1
      MIT

    • genmem

      helloSobuj
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that gives AI assistants long-term memory by storing, searching, and recalling notes as Markdown files on your machine.
      7 npm
      MIT

    • Obsidian MCP Server

      TheGreatAxios
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that enables AI assistants to securely read, create, and modify notes in an Obsidian vault, with support for semantic search and web scraping.
      6,222 npm
      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

    A3.9/5.0

    Scored across 19 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there is notable overlap between slipbox_remove_link and slipbox_delete_link, which differ only in error behavior. Additionally, slipbox_get_cluster_report with refresh=true and slipbox_refresh_clusters both regenerate cluster analysis, creating potential confusion.

    Naming Consistency5/5

    All tools share the slipbox_ prefix and follow a consistent verb_noun pattern (create_note, get_note, update_note, delete_note, create_link, delete_link, refresh_clusters). Verbs are clear and naming is uniform throughout, making the API predictable.

    Tool Count4/5

    19 tools is on the heavier side of the ideal range, but the count is justified by the comprehensive feature set: note CRUD, search, linking, tag management, cluster analysis, and maintenance. The slight excess is offset by each tool serving a clear purpose in the Zettelkasten workflow.

    Completeness5/5

    The tool set provides complete lifecycle coverage for notes (create, get, update, delete), robust search and exploration (search, similar, central, orphaned, by date, linked), rich linking capabilities (create, remove, delete, list links), and cluster management (report, create structure, refresh, dismiss). Also includes tag listing and index rebuild, leaving no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources