Task API MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK_API_BASE_URL | No | The base URL of the Task REST API | http://localhost:8000 |
| TASK_API_TIMEOUT_SECONDS | No | HTTP timeout in seconds for API calls | 10 |
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 |
|---|---|
| create_taskB | Create one task in the task management service. |
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 1 tool
Only one tool exists, so there is no possibility of confusion or overlap.
With a single tool, naming is trivially consistent; no pattern violations occur.
A task management service with only one creation tool is too thin; typical requires at least list, read, update, and delete operations.
The tool surface lacks critical operations like listing, retrieving, updating, and deleting tasks, leaving significant gaps for agents.