Skip to main content
Glama
jasongilman

Notes MCP

by jasongilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Notes MCP

No user-submitted related servers found.

    Related Servers

    • mcp-server-example

      VhMuzini
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage in-memory notes by listing, fetching, and creating notes through MCP tools over stdio.
      44 npm
      MIT

    • notes-mcp

      suhail1060
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing plain-text notes on disk through MCP resources, tools, and prompts, so natural-language requests can create, read, search, delete, and summarize notes via an interactive client.
      MIT

    • approveit MCP Server

      HJH0924
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A simple notes system that allows creating, storing, and accessing text notes through MCP resources and tools, with built-in prompt support for generating summaries of stored notes.
      -

    • memory-vault

      JohnXu22786
      A
      license
      A
      quality
      B
      maintenance
      Provides cross-session persistent memory for coding agents via MCP tools to store, retrieve, and manage notes with hybrid keyword/semantic search and automatic deduplication.
      8
      257 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

    A4.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to one distinct resource action (create, get, list, update, delete), with no overlapping operations. The descriptions reinforce boundaries by explaining when to use get_note over list_notes and create_note over update_note.

    Naming Consistency5/5

    All tool names follow the same verb_note pattern: create_note, get_note, list_notes, update_note, delete_note. list_notes is pluralized because it returns a collection, but the convention is otherwise uniform and predictable.

    Tool Count5/5

    Five tools form a tightly scoped set for a notes server: one create tool, one read tool, one list tool, one update tool, and one delete tool. Each tool earns its place and the count is ideal for the domain.

    Completeness5/5

    The tool surface covers the full note lifecycle with no dead ends: create, list, read by id, update, and delete. The update tool's replace-only behavior is mitigated by explicit guidance to call get_note first, so agents have a complete workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources