technical-notes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTES_DIR | Yes | Path to your notes directory |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_technical_notesA | Search local markdown and code files for a keyword and return the contents of the most relevant file. Searches the directory configured by the NOTES_DIR environment variable. |
| get_system_resource_usageA | Return the current CPU usage percentage and memory usage (used / total / percent) of the host machine. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve completely different purposes: one monitors system resources, the other searches technical notes. There is no risk of confusion.
Both tool names follow the 'verb_noun' pattern in snake_case, which is consistent and clear.
With only 2 tools, the server feels very thin. Moreover, the tools cover two unrelated domains (system monitoring and note searching), which is odd for a server named 'technical-notes-mcp'.
For a technical notes server, only a single search tool exists, lacking create, update, delete, or list operations. The system resource tool is out of place and does not address note management needs.