personal-timesheet-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMESHEET_API_BASE_URL | Yes | Base URL for the Timesheet Logger backend API |
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 |
|---|---|
| create_timesheet_entryB | Create a new timesheet entry with project, date, hours, and optional description |
| list_timesheet_entriesA | List timesheet entries with optional filters for date range, project, and pagination |
| get_timesheet_entryB | Get a single timesheet entry by ID |
| update_timesheet_entryC | Update an existing timesheet entry. Only provided fields will be updated. |
| delete_timesheet_entryB | Delete a timesheet entry by ID |
| list_projectsA | List all available projects that can be used for timesheet entries |
| create_projectB | Create a new project. Requires admin or manager role. |
| loginA | Login to your timesheet account via browser. Opens a browser window where you can enter your credentials. Use this after logout or to manually authenticate. |
| logoutA | Logout from the current timesheet session. Clears stored authentication tokens. You will need to re-authenticate (via browser login) on the next request. |
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 9 tools
Each tool targets a distinct action and resource. Login and logout are separate from project and timesheet entry operations, and CRUD tools for timesheet entries are clearly delineated.
Most tools follow a verb_noun pattern (e.g., create_project, list_timesheet_entries), but 'login' and 'logout' are single words, breaking the pattern slightly. Overall structure is clear.
With 9 tools spanning authentication, project management, and timesheet entry CRUD, the count is well-scoped for the domain without being excessive or thin.
Core workflows are covered: authentication, project listing and creation, and full CRUD on timesheet entries. Missing project update/delete, but these are less critical for typical timesheet use.