Skip to main content
Glama
pdegner

notes-mcp

by pdegner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NOTES_MCP_DIRNoDirectory to store notes (default: ~/.notes-mcp/notes/)

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
add_noteA

Save a new note.

Args:
    title: Short title for the note.
    content: The body of the note, as Markdown.
    tags: Optional labels for grouping, e.g. ["work", "ideas"].
list_notesA

List saved notes, most recently updated first.

Returns titles and tags only, not note bodies. Call get_note to read one.

Args:
    tag: Optional tag to filter by.
search_notesA

Find notes by text and/or tags.

Returns matching notes with a short snippet, not their full bodies. Call
get_note to read one in full.

Args:
    query: Text to look for in note titles and bodies (case-insensitive).
    tags: Only return notes carrying these tags.
    match_all: If true, a note must have every listed tag; otherwise any one
        of them is enough.
get_noteA

Read one note in full, including its body.

Args:
    note_id: The note's id, as returned by list_notes or search_notes.
delete_noteA

Delete a note permanently.

Args:
    note_id: The note's id, as returned by list_notes or search_notes.

Prompts

Interactive templates invoked by user choice

NameDescription
summarize_notesSummarize saved notes, optionally limited to one tag. Args: tag: Only summarize notes with this tag. Leave empty for all notes.

Resources

Contextual data attached and managed by the client

NameDescription
all_notes_indexAn index of every saved note: id, title, and tags.
tag_indexEvery tag in use, with the number of notes carrying it.
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: adding, listing (with metadata only), searching (with snippets), getting full content, and deleting. The list and search tools are complementary rather than overlapping, with explicit guidance to call get_note for full bodies.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern, but there is a minor inconsistency in pluralization: add_note, get_note, and delete_note use singular while list_notes and search_notes use plural. Despite this, the pattern is predictable and easy to follow.

Tool Count5/5

Five tools is well-scoped for a notes server, covering the essential operations (create, read, list, search, delete) without unnecessary bloat. Each tool has a clear role and contributes to the overall functionality.

Completeness4/5

The tool surface covers most of the CRUD lifecycle (add, list, get, search, delete) but lacks an update/edit operation, which is a common requirement for notes. This is a minor gap that can be worked around by deleting and re-adding, but it is not ideal.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources