TimePRO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMEPRO_API_KEY | Yes | Your personal access token | |
| TIMEPRO_API_URL | Yes | TimePRO base URL (e.g., https://ssw.sswtimepro.com) | |
| TIMEPRO_TENANT_ID | Yes | Your tenant ID (e.g., ssw) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clientsC | Search for clients to use in timesheets. Returns a list of clients with their IDs and names. |
| list_projectsB | Get projects for a specific client. Use this after selecting a client to find available projects. |
| list_categoriesB | Get available timesheet categories (e.g., Development, Meeting, Admin). These categorize the type of work done. |
| list_locationsB | Get available work locations (e.g., Office, Client Site, Remote). |
| get_timesheet_defaultsA | Get default values for creating a timesheet, including last used client, project, and rates. Call this before creating a timesheet to get sensible defaults. |
| list_timesheetsA | List timesheets for the current user within a date range. Returns summary information for each timesheet. |
| get_timesheetC | Get full details of a specific timesheet by its ID. |
| create_timesheetA | Create a new timesheet entry. Requires client, project, category, date, and time range. Returns the created timesheet ID. |
| update_timesheetB | Update an existing timesheet. All fields except timesheet_id are optional - only provided fields will be updated. |
| delete_timesheetC | Delete a timesheet by its ID. |
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
Each tool has a clearly distinct purpose with no ambiguity. Tools are organized around specific resources (timesheets, clients, projects, categories, locations) and actions (create, delete, get, list, update), making it easy for an agent to select the correct one without confusion.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_timesheet, list_clients, and update_timesheet. This predictability enhances readability and usability for agents navigating the tool set.
With 10 tools, the server is well-scoped for timesheet management, covering essential operations like CRUD for timesheets and listing related resources. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain.
The tool set provides complete coverage for timesheet management, including full CRUD operations (create, get, update, delete, list), support for related entities (clients, projects, categories, locations), and a utility tool for defaults. There are no obvious gaps that would hinder agent workflows.