TimeChimp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMECHIMP_API_KEY | Yes | Your TimeChimp API key. You can generate or copy this from the API section in your profile settings within your TimeChimp account. |
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 |
|---|---|
| get_projectsC | Retrieve all projects from TimeChimp |
| get_project_by_idC | Get a specific project by ID |
| create_projectC | Create a new project |
| update_projectC | Update an existing project |
| delete_projectC | Delete a project |
| get_project_insightsB | Get project insights including hours, budget, costs, and revenue data |
| get_usersC | Retrieve all users from TimeChimp |
| get_user_by_idC | Get a specific user by ID |
| create_userA | Create a new user (note: adding users can result in additional invoice and extra cost) |
| update_userC | Update an existing user |
| get_time_entriesC | Retrieve time entries from TimeChimp |
| get_time_entry_by_idC | Get a specific time entry by ID |
| get_contactsC | Retrieve all contacts from TimeChimp |
| get_contact_by_idC | Get a specific contact by ID |
| create_contactC | Create a new contact |
| update_contactC | Update an existing contact |
| delete_contactC | Delete a contact |
| get_customersC | Retrieve all customers from TimeChimp |
| get_customer_by_idC | Get a specific customer by ID |
| create_customerC | Create a new customer |
| update_customerC | Update an existing customer |
| delete_customerC | Delete a customer |
| get_tasksC | Retrieve all tasks from TimeChimp |
| get_task_by_idC | Get a specific task by ID |
| get_invoicesC | Retrieve all invoices from TimeChimp |
| get_invoice_by_idC | Get a specific invoice by ID |
| get_expensesC | Retrieve all expenses from TimeChimp |
| get_expense_by_idC | Get a specific expense by ID |
| create_expenseC | Create a new expense |
| update_expenseC | Update an existing expense |
| delete_expenseC | Delete an expense |
| update_expense_statusC | Update the status of expenses (internal approval/invoicing status) |
| update_expense_client_statusC | Update the client status of expenses (external approval/invoicing status) |
| get_expense_status_historyC | Query status history modification records of an expense |
| get_mileageC | Retrieve all mileage entries from TimeChimp |
| get_mileage_by_idB | Get a specific mileage entry by ID |
| create_mileageC | Create a new mileage entry |
| update_mileageC | Update an existing mileage entry |
| delete_mileageC | Delete a mileage entry |
| update_mileage_statusC | Update the status of mileage entries (internal approval/invoicing status) |
| update_mileage_client_statusC | Update the client status of mileage entries (external approval/invoicing status) |
| get_mileage_status_historyC | Query status history modification records of a mileage entry |
| get_mileage_vehiclesC | Retrieve all mileage vehicles from TimeChimp |
| get_mileage_vehicle_by_idC | Get a specific mileage vehicle by ID |
| get_tagsC | Retrieve all tags from TimeChimp |
| get_tag_by_idC | Get a specific tag by 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 46 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (contact, customer, expense, etc.) and action (create, get, update, delete), making it easy to tell them apart. The only potential overlap is between general update tools and specific status update tools, but their descriptions clarify the distinction.
Tool names follow a highly consistent verb_noun pattern throughout. All tools use snake_case with clear action prefixes (create_, get_, update_, delete_) followed by the resource name, with occasional modifiers like _by_id or _status_history. There are no deviations in naming conventions.
With 46 tools, the count is excessive for most MCP server purposes. While TimeChimp appears to be a comprehensive time tracking/expense management system, this many tools creates cognitive overhead and suggests the surface could be simplified through parameterization or resource grouping. A more focused set of 15-25 tools would likely suffice.
The tool surface provides complete CRUD/lifecycle coverage for all major domain entities (contacts, customers, expenses, mileage, projects, users, invoices, tags, tasks, time entries). There are no obvious gaps - every resource has create, read, update, and delete operations where appropriate, plus specialized operations like status updates and insights retrieval.