Amazing Marvin MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMAZING_MARVIN_API_KEY | Yes | Your Amazing Marvin API key, obtained from Settings → API in Amazing Marvin. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tasksA | Get today's scheduled tasks only. Use when you need only today's scheduled items without overdue or completed items. For comprehensive daily overview, use get_daily_productivity_overview() instead. For all tasks across projects, use get_all_tasks(). |
| get_projectsA | Get all projects (categories with type 'project'). Use when you need project list for organization or project selection. For detailed project analysis, use get_project_overview(project_id). |
| get_categoriesC | Get categories from Amazing Marvin |
| get_due_itemsA | Get overdue and due tasks only (past due date). Use when you need to focus specifically on urgent/overdue items. For complete daily view including today's tasks, use get_daily_productivity_overview(). |
| get_child_tasksA | Get child tasks of a specific parent task or project (experimental). Use when you need to see subtasks within a project or parent task. Returns both tasks and sub-projects. Set recursive=True for deep hierarchy. |
| get_all_tasksA | Get all tasks across all projects with optional label filtering (comprehensive search). Use when you need to search/filter across your entire task system. For daily focus, use get_daily_productivity_overview() instead. |
| get_labelsC | Get all labels from Amazing Marvin |
| get_goalsC | Get all goals from Amazing Marvin |
| get_account_infoC | Get account information from Amazing Marvin |
| get_currently_tracked_itemC | Get currently tracked item from Amazing Marvin |
| create_taskB | Create a new task in Amazing Marvin. |
| mark_task_doneC | Mark a task as completed in Amazing Marvin. |
| test_api_connectionA | Test the API connection and credentials. Use when troubleshooting connection issues or verifying API setup. Returns "OK" if successful or error details if failed. |
| start_time_trackingA | Start time tracking for a specific task. Use when beginning focused work on a task to measure time spent. Check current tracking status with get_currently_tracked_item() or time_tracking_summary(). Stop tracking with stop_time_tracking(task_id). |
| stop_time_trackingC | Stop time tracking for a specific task |
| get_time_tracksC | Get time tracking data for specific tasks |
| claim_reward_pointsC | Claim reward points for completing a task |
| get_kudos_infoC | Get kudos and achievement information |
| create_projectC | Create a new project in Amazing Marvin |
| create_project_with_tasksC | Create a project with multiple tasks at once |
| get_project_overviewC | Get comprehensive overview of a project including tasks and progress |
| get_daily_productivity_overviewA | Get comprehensive daily productivity overview with today's tasks, overdue items, completed items, and planning insights. Primary tool for daily planning and productivity. Consolidates multiple data sources efficiently. Use when you need a complete view of today's work situation. For specific data only, use: get_tasks() (today's scheduled), get_due_items() (overdue), get_all_tasks() (comprehensive search), or get_completed_tasks() (recent completions). |
| batch_create_tasksB | Create multiple tasks at once with optional project/category assignment |
| batch_mark_doneC | Mark multiple tasks as done at once |
| time_tracking_summaryA | Get time tracking overview and productivity insights. Use when you need to check current time tracking status and get productivity metrics. For starting/stopping tracking, use start_time_tracking() or stop_time_tracking(). For daily productivity overview, use get_daily_productivity_overview(). |
| get_completed_tasksA | Get completed tasks from past 7 days with efficient date filtering and categorization. Use when you need to review recent accomplishments or productivity patterns. For specific date, use get_completed_tasks_for_date(date). For custom time ranges, use get_productivity_summary_for_time_range(). |
| get_productivity_summary_for_time_rangeC | Get a comprehensive productivity summary for a specified time range |
| get_completed_tasks_for_dateB | Get completed tasks for a specific date using efficient API filtering |
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 28 tools
Most tools have distinct purposes, especially the task retrieval tools which are clearly differentiated by descriptions (e.g., get_all_tasks for comprehensive search, get_tasks for today's scheduled, get_due_items for overdue). However, there is still some overlap that could cause confusion for an agent, such as multiple ways to get completed tasks.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_task, mark_task_done, get_projects). Even batch operations follow the same pattern. No mixing of conventions, making it predictable and easy to understand.
With 28 tools, the server covers a wide range of functionality for a task management system (CRUD, time tracking, goals, kudos, etc.). While slightly above the ideal range, each tool serves a specific purpose and there are no unnecessary duplicates. A few tools could potentially be merged but overall it's well-scoped.
The tool set is notably incomplete for a task management system. There is no tool to update existing tasks (e.g., change title, due date, or description) nor to delete tasks permanently. The missing update and delete operations are significant gaps that will limit an agent's ability to fully manage tasks.