Skip to main content
Glama
vedantparmar12

Sticky Notes MCP Server

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
Append a new note to the sticky note file.

Args:
    message (str): The note content to be added.

Returns:
    str: Confirmation message indicating the note was saved.
read_notesA
Read and return all notes from the sticky note file.

Returns:
    str: All notes as a single string separated by line breaks.
         If no notes exist, a default message is returned.
save_to_new_fileB
Save content to a new notes file.

Args:
    filename (str): Name of the new file to create.
    content (str): Content to save in the new file.

Returns:
    str: Confirmation message indicating the content was saved.
delete_notesA
Delete all notes from the sticky note file.

Returns:
    str: Confirmation message indicating the notes were deleted.

Prompts

Interactive templates invoked by user choice

NameDescription
note_summary_prompt Generate a prompt asking the AI to summarize all current notes. Returns: str: A prompt string that includes all notes and asks for a summary. If no notes exist, a message will be shown indicating that.

Resources

Contextual data attached and managed by the client

NameDescription
get_latest_note Get the most recently added note from the sticky note file. Returns: str: The last note entry. If no notes exist, a default message is returned.

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a clearly distinct purpose: adding to the note file, reading all notes, creating a new notes file, and deleting all notes. No two tools perform the same action, so an agent can confidently select the right one.

Naming Consistency4/5

Tool names follow a mostly consistent verb-noun pattern (add_note, read_notes, delete_notes). The exception is save_to_new_file, which has a more complex verb-phrase structure, but it still uses the same snake_case style and starts with a verb, so the overall pattern remains readable.

Tool Count5/5

Four tools is well-scoped for a sticky notes server: one to add, one to read, one to delete, and one to save to a new file. Each tool earns its place without unnecessary bloat.

Completeness2/5

The set is missing essential operations for managing individual notes. There is no way to update a specific note or delete a single note, forcing users to delete all notes and re-add the ones they want to keep. This is a significant gap for a note-taking tool.

Maintenance

ActivityInactive
ResponsivenessNo issues