goodday-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOODDAY_API_TOKEN | Yes | Your Goodday API token |
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 |
|---|---|
| get_projectsB | Get list of projects from Goodday. Args: archived: Set to true to retrieve archived/closed projects root_only: Set to true to return only root projects |
| get_projectB | Get details of a specific project. Args: project_id: The ID of the project to retrieve |
| create_projectB | Create a new project in Goodday. Args: name: Project name created_by_user_id: ID of user creating the project project_template_id: Project template ID (found in Organization settings → Project templates) parent_project_id: Parent project ID to create a sub project color: Project color (1-24) project_owner_user_id: Project owner user ID start_date: Project start date (YYYY-MM-DD) end_date: Project end date (YYYY-MM-DD) deadline: Project deadline (YYYY-MM-DD) |
| get_project_tasksB | Get tasks from a specific project. Args: project_id: The ID of the project closed: Set to true to retrieve all open and closed tasks subfolders: Set to true to return tasks from project subfolders |
| get_user_assigned_tasksB | Get tasks assigned to a specific user. Args: user_id: The ID of the user closed: Set to true to retrieve all open and closed tasks |
| get_user_action_required_tasksC | Get action required tasks for a specific user. Args: user_id: The ID of the user |
| get_taskC | Get details of a specific task. Args: task_id: The ID of the task to retrieve |
| create_taskB | Create a new task in Goodday. Args:
project_id: Task project ID
title: Task title
from_user_id: Task created by user ID |
| update_task_statusC | Update the status of a task. Args: task_id: The ID of the task to update user_id: User on behalf of whom API will execute update status_id: New status ID message: Optional comment |
| add_task_commentC | Add a comment to a task. Args: task_id: The ID of the task user_id: User on behalf of whom API will execute update message: Comment text |
| get_usersB | Get list of organization users. |
| get_userB | Get details of a specific user. Args: user_id: The ID of the user to retrieve |
| get_project_usersB | Get users associated with a specific project. Args: project_id: The ID of the project |
| get_task_detailsB | Get comprehensive task details including subtasks, custom fields, and full metadata. Args: task_short_id: The short ID of the task (e.g., RAD-434) project_name: The name of the project containing the task (required, case-insensitive) |
| get_task_messagesB | Retrieve all messages/comments for a specific task. Args: task_short_id: The short ID of the task (e.g., RAD-434) project_name: Optional project name for disambiguation |
| get_goodday_sprint_tasksB | Get tasks from a specific sprint by project name and sprint name/number. Args: project_name: The name of the main project (e.g., "ASTRA") sprint_name: The name or number of the sprint (e.g., "Sprint 233", "233") include_closed: Whether to include closed tasks (default: True) |
| get_goodday_sprint_summaryB | Generate a comprehensive sprint summary with task details, status distribution, and key metrics. Args: project_name: The name of the main project (e.g., "ASTRA") sprint_name: The name or number of the sprint (e.g., "Sprint 233", "233") |
| get_goodday_smart_queryB | Natural language interface for common project management queries. Args: query: Natural language query (e.g., "show me all tasks assigned to John", "what projects do I have") |
| search_goodday_tasksB | Search for tasks using vector similarity search with optional filters. Args: query: Search query (natural language) limit: Maximum number of results to return (default: 10, max: 50) project_name: Optional project name filter (case-insensitive partial match) user_name: Optional user name/email filter for assigned tasks include_closed: Whether to include closed/completed tasks (default: False) |
| search_project_documentsB | Search for documents in a specific project. Args: project_name: The name of the project to search in (case-insensitive) document_name: Optional document name to filter by (case-insensitive partial match) include_content: Whether to include the full content of each document |
| get_document_contentC | Get the content of a specific document by its ID. Args: document_id: The ID of the document to retrieve |
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 21 tools
Most tools have distinct purposes, but there is notable overlap between get_task and get_task_details, and between get_project_tasks and get_goodday_sprint_tasks, which could cause confusion. Additionally, get_goodday_smart_query overlaps with several search and retrieval tools, though its natural language interface is a differentiating factor.
The naming follows a consistent verb_noun pattern (e.g., create_project, get_task, update_task_status) with minor deviations like get_goodday_smart_query and search_goodday_tasks that include 'goodday' inconsistently. Overall, the pattern is clear and readable, with only slight inconsistencies.
With 21 tools, the count is on the higher side for a project management server, bordering on heavy. While it covers many aspects, some tools might be redundant or could be consolidated, making it feel slightly bloated but still within a reasonable range for the domain.
The toolset provides comprehensive coverage for project and task management, including CRUD operations for projects, tasks, and comments, as well as retrieval for users, documents, and sprints. Minor gaps include lack of update/delete for projects and tasks, and no direct document creation tool, but core workflows are well-supported.