MCP Index Notes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_PATH | No | Path for SQLite database | ./data/notes.db |
| LOG_LEVEL | No | Pino logging level (trace|debug|info|warn|error) | |
| LOG_PRETTY | No | Set to true for human-readable logs |
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 |
|---|---|
| index-upsertC | Create or update a note under a key. Returns the note id. |
| image-upsertC | Store an image (base64 data or file path) under a key. Returns image id. |
| image-getC | Retrieve images by id or key. Optionally include base64 data. |
| image-deleteC | Delete an image by id or all images by key. |
| image-exportC | Export images (by id or key) to files. Returns file paths. |
| index-queryC | Query notes by key or full-text search. |
| index-deleteC | Delete notes by id or by key. Returns count/boolean. |
| index-backupC | Export all notes to a JSON backup file and return the path. |
| index-restoreC | Restore notes from a JSON backup file. Returns imported count. |
| index-list-keysC | List known keys and counts. |
| index-healthD | Health check. |
| graph-node-upsertC | Create or update a graph node with label/type/props. Returns node id. |
| graph-neighborsC | Get neighbors of a node (by id or label/type) up to a depth and limit. |
| graph-pathC | Find a path of nodes from A to B (by id or label/type). |
| graph-import-from-notesC | Import nodes and edges from existing notes: note -> key and note -> tags. |
| graph-statsB | Get counts of nodes and edges in the graph store. |
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 16 tools
Most tools have distinct purposes, but some overlap exists: 'graph-neighbors' and 'graph-path' both involve graph traversal, which could cause minor confusion. However, descriptions clarify that 'graph-neighbors' retrieves connected nodes while 'graph-path' finds specific paths, helping to differentiate them. Other tools like 'index-query' and 'index-list-keys' are clearly separate in function.
Tool names follow a highly consistent pattern throughout, using a clear 'category-action' format (e.g., 'graph-import-from-notes', 'image-delete', 'index-backup'). This consistency makes it easy to predict tool purposes and group related operations, with no deviations or mixed conventions observed.
With 16 tools, the count is slightly high but reasonable for the server's scope, which covers graph operations, image management, and note indexing. It feels comprehensive without being overwhelming, though a few tools like 'index-health' might be considered optional, slightly reducing efficiency.
The tool set provides complete coverage for the domain of note and graph management, including CRUD operations (e.g., upsert, delete, get), querying, backup/restore, and health checks. There are no obvious gaps; agents can perform full lifecycles for notes, images, and graph nodes without dead ends.