Fastidious MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTIDIOUS_URL | No | Fastidious API base URL | http://localhost:3000 |
| FASTIDIOUS_TOKEN | Yes | Authentication token for Fastidious API |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_noteB | Create a new note in Fastidious. Notes should be in Markdown format. |
| get_noteA | Get a specific note by ID with its full content |
| update_noteC | Update an existing note |
| delete_noteC | Delete a note by ID |
| list_notesB | List all notes, optionally filtered by parent collection |
| search_notesC | Search notes by content |
| create_collectionB | Create a new collection to organize notes |
| update_collectionB | Update a collection's settings, including field definitions |
| get_collectionB | Get a collection by ID, optionally including its children |
| list_collectionsB | List all collections at root level or within a parent |
| move_noteC | Move a note or collection to a different parent collection |
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 11 tools
Tools target distinct resources and actions, so an agent can easily distinguish create/get/update/delete/list for notes. The only wrinkle is move_note, which also moves collections despite being named for notes, creating minor ambiguity about where collection moves belong.
All 11 tools follow a clean verb_noun snake_case pattern (create_note, list_collections, move_note, etc.). Conventions are applied uniformly across both note and collection resources.
Eleven tools is well within a reasonable range and each one covers a distinct capability (CRUD, listing, searching, organizing). No redundant or filler tools pad the surface.
Notes have full CRUD plus list and search, but collections lack a delete operation and there is no delete_collection or collection search, leaving an obvious lifecycle gap. A move operation exists only under move_note rather than a symmetric resource-level naming.