hubstify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUBSTAFF_TOKEN_STORE | No | Path for the persisted token cache (default ~/.hubstify-mcp/token.json) | ~/.hubstify-mcp/token.json |
| HUBSTAFF_REFRESH_TOKEN | Yes | Personal Access Token (refresh token) |
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 |
|---|---|
| hubstaff_get_current_userA | Get the authenticated Hubstaff user (the owner of the access token). |
| hubstaff_list_organizationsA | List Hubstaff organizations the authenticated user has access to. Use the returned organization id for project, member and activity tools. |
| hubstaff_list_projectsB | List projects within an organization. |
| hubstaff_get_projectB | Get a single project by id. |
| hubstaff_list_membersB | List members (users) of an organization. |
| hubstaff_list_tasksC | List tasks belonging to a project. |
| hubstaff_create_taskC | Create a new task within a project. |
| hubstaff_list_activitiesC | List tracked time activities for an organization within a time range. Times are ISO 8601 (e.g. 2024-01-01T00:00:00Z). |
| hubstaff_daily_activitiesA | Get per-day aggregated tracked-time activities for an organization over a date range (dates are YYYY-MM-DD). |
| hubstaff_raw_requestA | Perform an arbitrary authenticated request against the Hubstaff v2 API. Use this for endpoints not covered by a dedicated tool. Path is relative to https://api.hubstaff.com/v2 (e.g. '/organizations'). |
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 10 tools
Most tools have clearly distinct purposes. However, `daily_activities` and `list_activities` both deal with tracked time and could cause confusion if an agent does not read the descriptions carefully.
The `hubstaff_` prefix is consistent, but the verb pattern is mixed: most use verb_noun (e.g., `list_projects`, `create_task`), but `daily_activities` uses an adjective instead of a verb, and `raw_request` is adjective_noun. `get_` vs `list_` is acceptable for single vs multiple.
10 tools is well-scoped for a Hubstaff API client. Each tool covers a distinct resource (organizations, projects, tasks, members, activities, current user) and the set is not overwhelming.
Core read and create operations are present for tasks, projects, and activities. However, there are no update or delete tools for any resource, and time tracking actions like start/stop are missing. The `raw_request` tool can fill gaps but reduces the dedicated surface.