idea-vault-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IDEA_VAULT_DB_PATH | No | Database file; parent directories and schema are created on startup | ~/.local/share/idea-vault/ideas.sqlite3 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| record_ideaC | Capture a new idea in the local vault. Returns the stored idea with its id. |
| list_ideasB | List ideas filtered by project, status (default open), category and priority. |
| search_ideasB | Search ideas by title, description or tags (case-insensitive substring match). |
| update_idea_statusB | Transition an idea to open, in_progress, completed or archived. |
| export_ideas_markdownA | Export one project's open and in-progress ideas as grouped GitHub-style markdown. |
| post_board_noteC | Post an asynchronous note to the shared blackboard for other agents. |
| read_board_notesB | Read blackboard notes for a project, unread only by default, optionally marking them read. |
| clear_board_notesB | Delete handled blackboard notes: read notes only by default, or every note with include_unread. |
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 8 tools
Most tools have clearly distinct purposes: record_idea vs post_board_note separate ideas from notes, and board note tools are unambiguous. However list_ideas and search_ideas could be confused at a glance, since both retrieve ideas and rely on descriptions to distinguish filtering from substring search.
All tools follow a consistent snake_case verb_noun pattern (record_idea, list_ideas, search_ideas, update_idea_status, export_ideas_markdown, post_board_note, read_board_notes, clear_board_notes). Minor singular/plural variation (idea vs ideas) does not break predictability.
Eight tools is well-scoped for an idea vault with an auxiliary blackboard. Each tool earns its place: core idea lifecycle plus note posting/reading/clearing, with no excessive or trivial tools.
Ideas support create, list, search, status update, and export, but there is no tool to update an idea's title, description, tags, category, or priority, and no delete/get-single-idea operation. This is a notable gap for a vault where captured ideas often need editing beyond status changes.