project-notes MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_noteC | Add a note about the project |
| search_notesC | Search notes by keyword |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| notes://summary |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one creates notes, the other searches them. There is no ambiguity in their purposes.
Both tools follow a verb_noun pattern, but one uses singular 'note' and the other plural 'notes', creating a minor inconsistency. The pattern is otherwise predictable and readable.
With only 2 tools, the server feels thin for a project-notes domain. The count matches the minimal add/search functionality, but it borders on insufficient for a well-scoped tool set.
The domain is note management, but the surface only supports adding and searching. Missing core operations like getting a specific note, updating, deleting, or listing all notes creates significant gaps that will force agents to work around missing functionality.