worksnaps-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKSNAPS_BASE_URL | No | API base URL (default https://api.worksnaps.com/api) | https://api.worksnaps.com/api |
| WORKSNAPS_API_TOKEN | Yes | API token from Worksnaps (Profile & Settings → Web Service API) | |
| WORKSNAPS_DEFAULT_TASK_ID | No | Default task ID for log_time | |
| WORKSNAPS_DEFAULT_PROJECT_ID | No | Default project ID for log_time |
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 | Resolve the current Worksnaps user from the API token (GET /me.xml). Returns user id, login, name, and email. |
| list_projectsB | List Worksnaps projects the current user can access (GET /projects.xml). |
| list_tasksB | List tasks in a Worksnaps project (GET /projects/{projectId}/tasks.xml). |
| log_timeA | Log offline time to Worksnaps for yourself (POST /projects/{projectId}/time_entries.xml). Requires projectId, taskId, and minutes. |
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 4 tools
Each tool targets a distinct resource: projects, tasks, time entries, and user identity. There is no ambiguity between them.
Most tools follow a verb_noun pattern (list_projects, list_tasks, log_time). 'whoami' deviates slightly but is still an imperative verb. Overall consistent.
With 4 tools, the server is focused and well-scoped for its purpose. Each tool serves a clear need without bloat.
The tool surface lacks read operations for logged time entries and lacks CRUD for projects and tasks. Users cannot retrieve, update, or delete time entries, which is a significant gap.