Skip to main content
Glama
michaelkrauty

mcp-notes

by michaelkrauty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-notes

No user-submitted related servers found.

    Related Servers

    • Notes MCP Server

      namp10010
      A
      license
      Not graded
      quality
      D
      maintenance
      A local note-taking server that provides intelligent management of markdown files through hybrid keyword and AI-powered semantic search. It enables users to create, find, and retrieve notes using advanced indexing, vector embeddings, and a built-in web viewer.
      MIT

    • obsidian-kb

      sanieni6
      F
      license
      C
      quality
      D
      maintenance
      Git-backed MCP server for creating and maintaining an Obsidian-style markdown knowledge base with full CRUD, search, and git sync.
      7
      -

    • mcp-markdown-vault

      wirux
      A
      license
      B
      quality
      C
      maintenance
      Headless semantic MCP server for Obsidian, Logseq, Dendron, Foam, and any markdown folder. Features built-in hybrid semantic search, surgical AST editing, template scaffolding, zero-config local embeddings, and workflow tracking.
      5
      20 npm
      12
      MIT

    • knowledgebased

      devkanro
      A
      license
      A
      quality
      D
      maintenance
      Provides semantic search and a tag-based knowledge graph for any project, auto-discovering local markdown knowledge bases with YAML frontmatter.
      10
      2 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

    B3.4/5.0

    Scored across 38 tools

    Disambiguation4/5

    Tool purposes are largely distinct and grouped by domain (notes, facts, glossary), with clear CRUD/search/maintenance roles. The only mild ambiguity is among fact retrieval options (query_facts/list_facts/search_facts) and the several fact-source integrity helpers, though their descriptions are specific enough for careful agents.

    Naming Consistency4/5

    Names consistently use snake_case verb-first patterns (create_note, delete_fact, merge_tags, search_glossary). Minor deviations like add_facts_batch, lookup_term, and get_facts_with_stale_sources slightly break the otherwise predictable verb_noun rhythm, and retrieval verbs (list/query/search/find) are not perfectly standardized.

    Tool Count2/5

    38 tools is well above the heavy threshold and will impose a real selection burden on agents. While the breadth reflects three subdomains plus maintenance features, several clusters (source-integrity tools, index/reindex tools, graph traversal) could be consolidated without losing core capability.

    Completeness4/5

    Notes, facts, and glossary all have full lifecycle coverage, plus search, history/restore, graph traversal, and integrity checks. Minor gaps exist—no explicit tag/category deletion, no direct source-record editing—but agents can work around them through update_note and revalidate/source tools.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources