TaskHub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASKHUB_API_URL | No | TaskHub backend API URL. Remote API URLs must use HTTPS. Plain HTTP is reserved for local development with localhost or 127.0.0.1. | http://localhost:3001/api |
| TASKHUB_API_TOKEN | Yes | The only credential: an opaque project-bound API key held in memory. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| taskhub_whoamiA | Show current user info, available scopes, and linked project context. |
| taskhub_contextA | Show the project linked to the current working directory. If no project is linked, automatically lists available projects so the user can choose one to connect. |
| taskhub_connectA | Link the current directory to a TaskHub project. Subsequent task operations will default to this project. Use project ID, slug, or systemCode to identify the project. |
| taskhub_searchB | Search any entity by its systemCode (e.g. TSK-260218-A3K7, ORG-260218-B2C3, PRJ-260218-D4F1). Returns the entity type and details. |
| taskhub_orgs_listA | List your organizations. |
| taskhub_org_createB | Create a new organization. |
| taskhub_org_membersB | List members of an organization. |
| taskhub_org_inviteC | Invite a user to an organization by email. |
| taskhub_projects_listA | List projects. Optionally filter by organization or personal projects. |
| taskhub_project_infoC | Get detailed information about a project, including members, statuses, and modules. |
| taskhub_project_createA | Create a new project. Specify organizationId for org project, or omit for personal project. |
| taskhub_project_inviteA | Invite a user to a project by email. |
| taskhub_project_membersA | List members of a project with their roles and user IDs. Useful for finding user IDs when assigning tasks. Auto-detects project from .taskhub.json if not specified. |
| taskhub_subproject_addA | Map a subdirectory to an existing TaskHub project (sub-project). Adds the mapping to .taskhub.json. If the project does not exist, creates it as a child of the root project. |
| taskhub_subproject_removeA | Remove a subdirectory mapping from .taskhub.json. Does NOT delete the project from TaskHub. |
| taskhub_statusesA | List available task statuses for a project or global statuses for daily tasks. IMPORTANT: Call this tool BEFORE creating or updating tasks so you know valid statusId values. Returns each status with its id, name, and flags (DEFAULT = auto-assigned to new tasks, COMPLETED = marks task as done). |
| taskhub_tasks_listA | List tasks with filters. Without explicit projectId, uses the project linked to the current directory. Supports filtering by status, type, assignee, and pagination. |
| taskhub_tasks_myB | Get tasks assigned to or created by me. |
| taskhub_tasks_dailyA | Get daily tasks for a specific date (defaults to today). |
| taskhub_task_getA | Get full details of a single task. Accepts UUID, systemCode (TSK-XXXXXX-XXXX), or a search term to find by title. Examples: taskhub_task_get({identifier: "TSK-260218-B0F3"}) or taskhub_task_get({identifier: "login"}). |
| taskhub_task_createA | Create a new task. IMPORTANT: Before calling this tool, ALWAYS ask the user to confirm: (1) whether this is a "project" task or a "daily" routine task, and (2) confirm the linked project context. When a project is linked via .taskhub.json, ALL tasks (project and daily) are associated to it by default. Only omit projectId if the user explicitly says the task is not related to any project. If projectId differs from the linked project, a warning is shown. |
| taskhub_task_updateA | Update a task. Specify the task ID and any fields to change. TIP: To change status, first call taskhub_statuses to get valid statusId values for the project. |
| taskhub_task_ai_usage_recordA | Record one provider-agnostic AI usage execution for a task. Usage must come from the reporting client; this tool never estimates tokens from task content. |
| taskhub_task_completeB | Mark a task as completed. Automatically finds the "completed" status for the task's project (using the isCompleted flag) and applies it. |
| taskhub_subtask_createA | Create a subtask under an existing task. |
| taskhub_task_deleteA | Delete a task. IMPORTANT: Always confirm with the user before calling this tool. Set confirm=true to execute the deletion. Without confirm=true, it only shows what WOULD be deleted. |
| taskhub_commentsB | List comments on a task. |
| taskhub_comment_addA | Add a comment to a task. |
| taskhub_notificationsB | List your notifications with unread count. |
| taskhub_notification_readA | Mark a notification as read, or mark all notifications as read. |
| taskhub_daily_summaryB | Get a summary of your activity for a specific day (defaults to today). Shows tasks created, completed, comments added, and activity log. |
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 31 tools
Most tools map clearly to a distinct entity+action, but there are a few close boundaries: search vs. task_get both resolve by systemCode, whoami vs. context both expose linked project context, and task_complete is a specialized task_update. Detailed descriptions mitigate most confusion.
A general noun_verb pattern is visible (task_create, project_invite), but list endpoints are inconsistent: some use _list (orgs_list, tasks_list) while others use bare plurals (comments, notifications, statuses). Irregular names like whoami, connect, tasks_my, and daily_summary break the pattern further, though the naming remains readable.
With 31 tools, the server exceeds the 25-tool threshold for 'too many' in the calibration. The broad domain justifies some surface area, but utilities like whoami, search, and daily_summary could be consolidated with existing list/context tools to reduce redundancy.
Core task operations are well covered: list, get, create, update, complete, delete, and subtasks. However, org and project management lack update/delete operations, comments only support list/add with no edit/delete, and there is no member removal—leaving notable gaps for project administration workflows.