Task360 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK360_EMAIL | No | Email address for login credentials authentication. Must be used together with TASK360_PASSWORD. | |
| TASK360_PASSWORD | No | Password for login credentials authentication. Must be used together with TASK360_EMAIL. | |
| TASK360_SESSIONID | No | Session ID cookie from task.chat360.io for session-based authentication. Can be used as an alternative to TASK360_EMAIL and TASK360_PASSWORD. | |
| TASK360_WORKSPACE | No | Optional default workspace. Example: chat360. | chat360 |
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 |
|---|---|
| list_workspacesA | List all Task360 workspaces available to the authenticated user. |
| get_user_profileB | Get the current signed-in Task360 user profile and details. |
| get_my_ticketsA | Fetch tickets assigned to the authenticated user in the specified workspace. Args: workspace: Workspace slug (optional, defaults to configured or primary workspace). limit: Maximum number of tickets to retrieve (default: 50). |
| search_ticketsB | Search and list work items (tickets) in a workspace. Args: query: JQL-like search query string, e.g. "status = in_progress" or "assignee = currentUser()". assignee_id: Filter by assignee user ID. status_id: Filter by status ID. project_id: Filter by project ID. workspace: Workspace slug (optional). limit: Maximum number of tickets (default: 50). |
| get_ticketA | Retrieve full details of a specific ticket by key (e.g. CPD-123). Args: key: The work item key (e.g. "CPD-123"). workspace: Workspace slug (optional). |
| update_ticketB | Update fields of an existing ticket. Args: key: The work item key (e.g. "CPD-123"). summary: New ticket title/summary. description: New ticket description. assignee_id: User ID to assign to (or None). extra_fields: Additional fields dict (e.g. {"board": 1, "sprint": 2}). workspace: Workspace slug (optional). |
| get_transitionsB | Get available status workflow transitions for a ticket. Args: key: The work item key (e.g. "CPD-123"). workspace: Workspace slug (optional). |
| transition_ticketB | Change the workflow status of a ticket by executing a transition. Args: key: The work item key (e.g. "CPD-123"). transition_id: The ID of the transition to execute (use get_transitions to list IDs). workspace: Workspace slug (optional). |
| add_commentB | Add a comment to a ticket. Args: key: The work item key (e.g. "CPD-123"). body: Comment markdown text. workspace: Workspace slug (optional). |
| delete_ticketB | Permanently delete a ticket. Args: key: The work item key (e.g. "CPD-123"). workspace: Workspace slug (optional). |
| create_ticketC | Create a new ticket in Task360. Args: project_id: Project ID. item_type_id: Item type ID (e.g. Task, Bug). board_id: Board ID to place the ticket on. summary: Title/summary of the ticket. description: Detailed description of the ticket. assignee_id: Optional user ID to assign. extra_fields: Optional dictionary of additional fields. workspace: Workspace slug (optional). |
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 11 tools
Most tools have clearly distinct purposes tied to specific resources and actions. The only mild overlap is between get_ticket, get_my_tickets, and search_tickets, but descriptions clarify that one fetches by key while the others filter by assignee/query. get_transitions vs transition_ticket are also well differentiated (read vs execute).
The set follows a mostly predictable verb_noun pattern (get_ticket, update_ticket, delete_ticket, create_ticket, search_tickets). Minor deviations like transition_ticket (noun-as-verb) and the mix of get_/add_ verbs are readable but slightly inconsistent.
11 tools is well-scoped for a ticket management server, with each tool earning its place across read, write, search, workflow, and comment operations. No redundant or filler tools.
Ticket lifecycle is well covered with create, get, update, delete, plus workflow transitions and comments. Minor gaps exist on the comment side (no edit/delete comment) and workspace-level operations, but agents can work around these.