teamwork
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEAMWORK_SITE | No | Your Teamwork site URL or site name, overrides the keychain value. | |
| TEAMWORK_API_KEY | No | Your Teamwork personal API key, overrides the keychain value. Note: env vars are plaintext. |
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 |
|---|---|
| whoamiA | Return the Teamwork.com user that owns the configured API key, plus site URL and whether the user is an admin. |
| list_projectsB | List projects visible to the API key. Use search to filter by name; results are paged. |
| list_tasklistsB | List the task lists (columns/boards) inside a project. |
| list_tasksA | Search tasks across projects or within one project/task list. Completed tasks are excluded unless includeCompleted is true. |
| get_taskA | Fetch a single task with description and key fields. |
| create_taskB | Create a task inside a task list. |
| update_taskA | Update fields of an existing task, or mark it complete with complete=true. |
| latest_activityA | Chronological feed of recent activity across all projects (comments, task updates, files, milestones...). Mirrors the Teamwork activity widget. Filter by project, user, type or date range. |
| my_workA | Tasks assigned to the API key's user (responsible party): what is due today, overdue or coming this week. |
| searchA | Search tasks, messages, files, comments, milestones, notebooks and links across the site by keyword. |
| upcoming_milestonesB | Milestones with deadlines in a date range across projects. Defaults to the next 30 days. |
| project_updatesC | Latest status updates (health reports) posted on projects. |
| list_task_commentsB | Read the comment thread of a task. |
| list_peopleB | Find users (id, name, email) to use as assignees or in user filters. |
| add_task_commentA | Post a comment on a task. Use to report progress, answer questions or hand off work in the task thread. |
| log_timeC | Log a time entry (timesheet) on a task or a project. |
| auth_statusA | Check whether a Teamwork API key is configured on this machine, which site it points to and where it is stored. |
| logoutA | Remove the stored Teamwork API key from this machine (OS keychain + local file). The next tool call will ask to set up again. |
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 18 tools
Each tool targets a distinct resource or action: auth tools, project/task listing, task CRUD, comments, time logging, activity feeds, people lookup, and search. Even similar tools like list_tasks and my_work differ by scope (all tasks vs. assigned to user), and latest_activity vs. search are clearly differentiated by feed vs. keyword. No two tools appear to serve the same purpose.
Tools predominantly follow a clear verb_noun snake_case pattern (list_projects, create_task, update_task, log_time, add_task_comment). Exceptions like whoami, auth_status, and logout are idiomatic and consistent with the overall style, showing no mixed conventions or camelCase. The naming is predictable and aids agent selection.
18 tools is slightly above the ideal 3–15 range but justified by the breadth of the Teamwork.com domain: authentication, projects, task lists, tasks, comments, time, activity, milestones, project updates, and people. Each tool addresses a distinct need, so the count feels reasonable rather than bloated.
The surface covers task creation, retrieval, update, search, and comments, plus time logging and activity feeds. However, it lacks task deletion and any project or task list creation/update/delete operations, which are notable gaps for full lifecycle management. The absence of these operations could cause dead ends in workflows requiring them.