TaskMesh MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASKMESH_API_URL | Yes | The URL of the TaskMesh API server. | |
| TASKMESH_API_TOKEN | Yes | Personal access token for authenticating with the TaskMesh API. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all projects in the organization |
| get_projectA | Get detailed information of a specific project by ID |
| create_projectC | Create a new project |
| update_projectB | Update an existing project metadata or status |
| delete_projectB | Delete a project |
| add_workflow_statusB | Add a new workflow status to a project |
| list_issuesB | List issues with optional filters |
| get_issueB | Get detailed information of a specific issue by ID |
| create_issueC | Create a new issue inside a project |
| update_issueC | Update an existing issue status, assignee, estimate, or metadata |
| delete_issueC | Delete an issue |
| add_commentB | Add a discussion comment to an issue |
| list_sprintsA | List all sprints for a project |
| get_sprintB | Get detailed information of a specific sprint by ID |
| create_sprintB | Create a new sprint |
| update_sprintC | Update sprint details |
| start_sprintB | Start a planned sprint |
| complete_sprintA | Complete an active sprint and optionally roll over incomplete issues |
| delete_sprintB | Delete a sprint |
| log_timeC | Log time spent on an issue manually |
| list_time_entriesC | List logged time entries with filters |
| get_active_timerB | Get currently running timer for the authenticated user |
| start_timerB | Start a running stopwatch timer on a specific issue |
| stop_timerA | Stop the active running timer and save it as a time entry |
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 24 tools
All tools have clearly distinct purposes. Issues, sprints, projects, timers, time entries, comments, and workflow statuses are separate domains with no overlap.
All tools follow a consistent verb_noun pattern (e.g., create_issue, list_projects, start_timer), all in snake_case, making it easy for an agent to predict tool names.
24 tools is slightly above the ideal range but still well-proportioned for a project management server covering multiple entities (issues, sprints, projects, timers, etc.), each earning its place.
Core CRUD operations are covered for projects, issues, and sprints. Timer and time entry management are included. Minor gaps like deleting comments or advanced issue transitions are missing but do not severely hamper workflows.