Skip to main content
Glama
taiste

Harvest MCP Server

by taiste
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HARVEST_API_KEYYesYour Harvest API key for authentication
HARVEST_ACCOUNT_IDYesYour Harvest account ID for API access

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_usersA

List all users in your Harvest account.

Args:
    is_active: Pass true to only return active users and false to return inactive users
    page: The page number for pagination
    per_page: The number of records to return per page (1-2000)
get_user_detailsB

Retrieve details for a specific user.

Args:
    user_id: The ID of the user to retrieve
list_time_entriesB

List time entries with optional filtering.

Args:
    user_id: Filter by user ID
    from_date: Only return time entries with a spent_date on or after the given date (YYYY-MM-DD)
    to_date: Only return time entries with a spent_date on or before the given date (YYYY-MM-DD)
    is_running: Pass true to only return running time entries and false to return non-running time entries
create_time_entryC

Create a new time entry.

Args:
    project_id: The ID of the project to associate with the time entry
    task_id: The ID of the task to associate with the time entry
    spent_date: The date when the time was spent (YYYY-MM-DD)
    hours: The number of hours spent
    notes: Optional notes about the time entry
stop_timerB

Stop a running timer.

Args:
    time_entry_id: The ID of the running time entry to stop
start_timerC

Start a new timer.

Args:
    project_id: The ID of the project to associate with the time entry
    task_id: The ID of the task to associate with the time entry
    notes: Optional notes about the time entry
list_projectsB

List projects with optional filtering.

Args:
    client_id: Filter by client ID
    is_active: Pass true to only return active projects and false to return inactive projects
get_project_detailsC

Get detailed information about a specific project.

Args:
    project_id: The ID of the project to retrieve
list_clientsB

List clients with optional filtering.

Args:
    is_active: Pass true to only return active clients and false to return inactive clients
get_client_detailsC

Get detailed information about a specific client.

Args:
    client_id: The ID of the client to retrieve
list_tasksB

List all tasks with optional filtering.

Args:
    is_active: Pass true to only return active tasks and false to return inactive tasks

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

TDQS

A3.5/5.0

Scored across 11 tools

Disambiguation5/5

Every tool has a clearly distinct purpose targeting specific resources and actions. For example, create_time_entry vs. start_timer vs. stop_timer handle different aspects of time tracking, while list_* tools retrieve collections and get_* tools fetch individual details. No tools appear to overlap or cause confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case throughout. The naming is highly predictable: list_* for collections, get_* for details, create_* for creation, and start_/stop_ for timer actions. There are no deviations in style or convention.

Tool Count5/5

With 11 tools, this server is well-scoped for time tracking and project management. Each tool earns its place by covering essential operations like CRUD for time entries, listing resources, and timer control. The count is neither too sparse nor bloated for the domain.

Completeness4/5

The tool surface provides strong coverage for core time tracking workflows, including creating/listing time entries, managing timers, and accessing clients, projects, tasks, and users. A minor gap exists in missing update/delete operations for time entries and other resources, but agents can work around this with the available tools.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources