Skip to main content
Glama
pipinho13

MCP Notes Server

by pipinho13

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Create a new note.

Args:
    title: A short name for the note, e.g. "Groceries".
    content: The body text of the note.
update_noteA

Replace the content of an existing note.

Args:
    title: The title of the note to update.
    content: The new body text (overwrites the old content).
list_notesA

List the titles of all saved notes.

read_noteB

Read the full content of one note.

Args:
    title: The title of the note to read.
search_notesA

Find notes whose title or content contains the query (case-insensitive).

Args:
    query: The text to search for.
delete_noteA

Delete a note permanently.

Args:
    title: The title of the note to delete.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
all_notesA read-only snapshot of every note, concatenated. Resources are data Claude can load into its context on demand, as opposed to tools, which perform actions. This one lets Claude "see" all notes at once without calling a tool for each.

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool maps to a distinct operation: create, update, list, read, search, and delete. There is no overlap or ambiguity in their purposes.

Naming Consistency5/5

All tools follow a clear verb_noun pattern with the note resource. The only minor variation is pluralization for list_notes and search_notes, but this is consistent with typical collection-returning conventions.

Tool Count5/5

Six tools cover the full lifecycle of a notes domain without redundancy. The count is well-scoped and each tool earns its place.

Completeness5/5

The server provides complete CRUD coverage plus search, with no obvious gaps. Users can create, read, list, update, delete, and find notes effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues