mcp-teamline
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| teamline_auth_testA | Verify TEAMLINE_API_KEY against Teamline auth.test and return the authenticated user (id, name, email). Takes no arguments; the API token is read only from the environment. |
| teamline_tasks_listA | List Teamline tasks via tasks.list. Optional filters: limit, channel (#name or slackId), list (~name or id; channel required if list is set), user (@name, email, or slackId), complete (true = only completed). If channel and user are omitted, the API defaults to yourself. Token is read only from TEAMLINE_API_KEY. |
| teamline_tasks_createA | Create a Teamline task via tasks.create. name is required. Optional: description, assign (string[] of @name/email/slackId), channel (#name or slackId), list (~name or id; channel required if list is set), personal (boolean), due (ISO8601 or human string), notify (string[]). Token is read only from TEAMLINE_API_KEY. |
| teamline_tasks_completeA | Mark a Teamline task complete via tasks.complete. Requires task (id string). Token is read only from TEAMLINE_API_KEY. |
| teamline_webhooks_createA | Register a user-provided URL via webhooks.create. Official event is currently only tasks_completed. url is required; name is optional. This server registers the URL; the MCP stdio process does not receive Teamline POSTs. Token is read only from TEAMLINE_API_KEY. |
| teamline_webhooks_removeA | Remove a Teamline webhook via webhooks.remove. Requires hook (id string). Token is read only from TEAMLINE_API_KEY. |
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 6 tools
Tasks and webhooks are clearly separated by the teamline_ prefix and verb. Within tasks, list/create/complete are distinct operations, though list could be confused with create if an agent overlooks the verb. Webhooks create/remove are clearly distinct.
All tools follow a consistent teamline_<domain>_<verb> pattern (auth_test, tasks_list, tasks_create, tasks_complete, webhooks_create, webhooks_remove). The only minor deviation is 'auth_test' using a noun-verb inversion (test as verb) rather than 'test_auth', but it's readable and consistent in style.
Six tools is well-scoped for a task management integration. Each tool covers a distinct operation needed for basic task lifecycle and webhook management. No redundant tools, and the count feels appropriate (within the 3-15 ideal range).
The tools cover task list, create, and complete, but lack update (e.g., edit task name, due date, assignee) and delete operations. Webhooks support create/remove but no list. A user cannot edit an existing task without recreating it, which is a notable gap in a task management API.