amazing-marvin-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sync_marvinA | Force-refresh the local mirror from Marvin (normally automatic). |
| get_structureA | Category/project tree with ids and open-task counts, labels by group, strategies in use. Call this once at the start of a session; it is how you map names to ids. |
| list_inboxA | Open tasks in the Inbox (not filed in any category/project), oldest first. |
| list_todayB | What's on for a day: do date that day, do date earlier but not done, due by then. Args: day: YYYY-MM-DD or today/tomorrow/yesterday. |
| list_dueA | Open tasks with a Due date on or before a day (default: end of this week). Args: by: YYYY-MM-DD, today, tomorrow, week, next-week, month. limit: Maximum number of tasks to return. |
| search_tasksA | Find tasks by any combination of filters (all ANDead). Unset filters are ignored. This is the tool for "what can I do in 5 minutes", "everything tagged X", "what's scheduled this week in project Y", etc. |
| get_taskB | Full details of one task (note, subtasks, dates, tracking) or project (its open children). |
| list_childrenB | Open tasks and sub-projects directly inside a project/category (by id or name). |
| create_taskC | Create a task. Names for parent/labels are resolved here; don't use #/@ shortcuts. |
| create_projectC | Create a project (container for tasks). Convert an inbox item into one with this + update_task(parent=…). |
| update_taskA | Edit a task or project: rename, move, relabel, (re)schedule, deadlines, estimate, note. Only the arguments you pass are changed. Requires the full-access token. |
| update_subtasksA | Add, complete, reopen, rename or remove subtasks of a task. Requires full access. |
| create_categoryB | Create a category (a folder in the Master List). Categories can only live under categories. |
| create_labelA | Create a label (optionally inside an existing or new label group). Requires the Task Labels strategy to be enabled in Marvin. |
| mark_doneB | Mark a task or project done (handles recurring/echo tasks and stops tracking). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_inbox | Go through the inbox item by item, applying the user's triage checklist. |
| daily_review | Show what the user checks every day. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| workflow_resource | How this user works with Marvin (their own words), all sections. |
| structure_resource | Category/project tree, labels, and enabled strategies. |
TDQS
Scored across 15 tools
The list tools (list_inbox, list_today, list_due, search_tasks, list_children) all return tasks but with distinct scopes, and descriptions clarify when to use each. get_task and list_children overlap slightly for project children, but get_task provides full details while list_children is a focused listing.
All tools use snake_case with a consistent verb_noun pattern (get_*, list_*, create_*, update_*, search_tasks, mark_done, sync_marvin). No mixed conventions or vague names.
15 tools fit the task-management domain well, covering listing, search, CRUD, and subtask operations. Each tool has a clear, non-redundant purpose, staying within the typical 3-15 range.
Core CRUD is mostly covered (create, read, update, list, search, mark done), but there is no delete operation for tasks, projects, categories, or labels, and no way to reopen a completed task. These notable gaps could force workarounds or cause failures for cleanup/undo workflows.