Notes MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV_PUBLISH_TOKEN | No | PyPI token for publishing | |
| UV_PUBLISH_PASSWORD | No | PyPI password for publishing | |
| UV_PUBLISH_USERNAME | No | PyPI username for publishing |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add-noteC | Add a new note |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-notes | Creates a summary of all notes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'add-note' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The naming follows a consistent verb-noun pattern with 'add-note', and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable within this minimal set.
A single tool is too few for a server named 'Notes MCP Server', which implies a broader scope for managing notes (e.g., creating, reading, updating, deleting). This minimal set feels incomplete and under-scoped for the apparent domain.
The tool surface is severely incomplete for a notes management server. It only provides an 'add-note' tool, lacking essential operations like retrieving, updating, deleting, or listing notes, which will cause significant agent failures in typical workflows.