Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_stop_timer

Stop a running time entry timer in Harvest by providing the time entry ID. This tool halts active time tracking for accurate billing and project management.

Instructions

Stop a running time entry timer. Use about {"tool": "harvest_stop_timer"} for detailed workflow and examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTime entry ID

Implementation Reference

  • Core handler function that performs the API PATCH request to stop the time entry timer.
    async stopTimer(id: string) {
      return this.makeRequest(`/time_entries/${id}/stop`, {
        method: 'PATCH',
      });
    }
  • MCP server dispatch handler that calls the stopTimer method and formats the JSON response.
    case 'harvest_stop_timer':
      const stoppedTimer = await harvestClient.stopTimer(typedArgs.id as string);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(stoppedTimer, null, 2),
          },
        ],
      };
  • Tool definition with name, description, and input schema for MCP tool registration and validation.
    name: 'harvest_stop_timer',
    description: 'Stop a running time entry timer. Use about {"tool": "harvest_stop_timer"} for detailed workflow and examples.',
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Time entry ID' }
      },
      required: ['id']
    }
  • src/tools.ts:1-222 (registration)
    The tools array exports all tool definitions for registration in the MCP server.
    import { Tool } from '@modelcontextprotocol/sdk/types.js';
    
    export const tools: Tool[] = [
      // Time Entry Tools
      {
        name: 'harvest_list_time_entries',
        description: 'List time entries with optional filters. Use about {"tool": "harvest_list_time_entries"} for detailed usage examples.',
        inputSchema: {
          type: 'object',
          properties: {
            user_id: { type: 'string', description: 'Filter by user ID' },
            project_id: { type: 'string', description: 'Filter by project ID' },
            from: { type: 'string', description: 'Start date (YYYY-MM-DD)' },
            to: { type: 'string', description: 'End date (YYYY-MM-DD)' },
            page: { type: 'number', description: 'Page number' },
            per_page: { type: 'number', description: 'Results per page (max 100)' }
          }
        }
      },
      {
        name: 'harvest_create_time_entry',
        description: 'Create a new time entry. Use about {"tool": "harvest_create_time_entry"} for detailed parameters and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            project_id: { type: 'string', description: 'Project ID' },
            task_id: { type: 'string', description: 'Task ID' },
            spent_date: { type: 'string', description: 'Date of the entry (YYYY-MM-DD)' },
            hours: { type: 'number', description: 'Hours worked' },
            notes: { type: 'string', description: 'Notes for the time entry' }
          },
          required: ['project_id', 'task_id', 'spent_date']
        }
      },
      {
        name: 'harvest_update_time_entry',
        description: 'Update an existing time entry. Use about {"tool": "harvest_update_time_entry"} for detailed parameters and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            id: { type: 'string', description: 'Time entry ID' },
            project_id: { type: 'string', description: 'Project ID' },
            task_id: { type: 'string', description: 'Task ID' },
            spent_date: { type: 'string', description: 'Date of the entry (YYYY-MM-DD)' },
            hours: { type: 'number', description: 'Hours worked' },
            notes: { type: 'string', description: 'Notes for the time entry' }
          },
          required: ['id']
        }
      },
      {
        name: 'harvest_delete_time_entry',
        description: 'Delete a time entry. Use about {"tool": "harvest_delete_time_entry"} for detailed usage and warnings.',
        inputSchema: {
          type: 'object',
          properties: {
            id: { type: 'string', description: 'Time entry ID to delete' }
          },
          required: ['id']
        }
      },
      {
        name: 'harvest_restart_timer',
        description: 'Restart a stopped time entry timer. Use about {"tool": "harvest_restart_timer"} for detailed workflow and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            id: { type: 'string', description: 'Time entry ID' }
          },
          required: ['id']
        }
      },
      {
        name: 'harvest_stop_timer',
        description: 'Stop a running time entry timer. Use about {"tool": "harvest_stop_timer"} for detailed workflow and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            id: { type: 'string', description: 'Time entry ID' }
          },
          required: ['id']
        }
      },
      {
        name: 'about',
        description: 'Get detailed information about the Harvest MCP server and its tools. Call about without parameters for general info, or with {"tool": "tool_name"} for specific tool documentation.',
        inputSchema: {
          type: 'object',
          properties: {
            tool: { type: 'string', description: 'Optional: specific tool name to get detailed information about' }
          }
        }
      },
      {
        name: 'version',
        description: 'Get version information about the Harvest MCP server.',
        inputSchema: {
          type: 'object',
          properties: {}
        }
      },
    
      // Project Tools
      {
        name: 'harvest_list_projects',
        description: 'List all projects with filtering options. Use about {"tool": "harvest_list_projects"} for detailed parameters and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            is_active: { type: 'boolean', description: 'Filter by active status' },
            client_id: { type: 'string', description: 'Filter by client ID' },
            page: { type: 'number', description: 'Page number' },
            per_page: { type: 'number', description: 'Results per page (max 100)' }
          }
        }
      },
      {
        name: 'harvest_get_project',
        description: 'Get details of a specific project. Use about {"tool": "harvest_get_project"} for detailed usage examples.',
        inputSchema: {
          type: 'object',
          properties: {
            id: { type: 'string', description: 'Project ID' }
          },
          required: ['id']
        }
      },
    
      // Task Tools
      {
        name: 'harvest_list_tasks',
        description: 'List all tasks with filtering options. Use about {"tool": "harvest_list_tasks"} for detailed parameters and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            is_active: { type: 'boolean', description: 'Filter by active status' },
            page: { type: 'number', description: 'Page number' },
            per_page: { type: 'number', description: 'Results per page (max 100)' }
          }
        }
      },
    
      // User Tools
      {
        name: 'harvest_get_current_user',
        description: 'Get information about the authenticated user. Use about {"tool": "harvest_get_current_user"} for detailed response format.',
        inputSchema: {
          type: 'object',
          properties: {}
        }
      },
      {
        name: 'harvest_list_users',
        description: 'List all users in the account with filtering. Use about {"tool": "harvest_list_users"} for detailed parameters and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            is_active: { type: 'boolean', description: 'Filter by active status' },
            page: { type: 'number', description: 'Page number' },
            per_page: { type: 'number', description: 'Results per page (max 100)' }
          }
        }
      },
    
      // Client Tools
      {
        name: 'harvest_list_clients',
        description: 'List all clients with filtering options. Use about {"tool": "harvest_list_clients"} for detailed parameters and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            is_active: { type: 'boolean', description: 'Filter by active status' },
            page: { type: 'number', description: 'Page number' },
            per_page: { type: 'number', description: 'Results per page (max 100)' }
          }
        }
      },
    
      // Report Tools
      {
        name: 'harvest_time_report',
        description: 'Generate detailed time reports for date ranges. Use about {"tool": "harvest_time_report"} for filtering options and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            from: { type: 'string', description: 'Start date (YYYY-MM-DD)' },
            to: { type: 'string', description: 'End date (YYYY-MM-DD)' },
            user_id: { type: 'string', description: 'Filter by user ID' },
            project_id: { type: 'string', description: 'Filter by project ID' },
            client_id: { type: 'string', description: 'Filter by client ID' }
          },
          required: ['from', 'to']
        }
      },
    
      // Assignment Tools
      {
        name: 'harvest_list_project_assignments',
        description: 'List project assignments for the current user. Use about {"tool": "harvest_list_project_assignments"} for detailed usage.',
        inputSchema: {
          type: 'object',
          properties: {
            page: { type: 'number', description: 'Page number' },
            per_page: { type: 'number', description: 'Results per page (max 100)' }
          }
        }
      },
      {
        name: 'harvest_list_task_assignments',
        description: 'List task assignments for a project. Use about {"tool": "harvest_list_task_assignments"} for detailed workflow and examples.',
        inputSchema: {
          type: 'object',
          properties: {
            project_id: { type: 'string', description: 'Project ID' },
            is_active: { type: 'boolean', description: 'Filter by active status' },
            page: { type: 'number', description: 'Page number' },
            per_page: { type: 'number', description: 'Results per page (max 100)' }
          },
          required: ['project_id']
        }
      }
    ];
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Stop a running time entry timer') but lacks critical details: whether this requires specific permissions, what happens to the stopped time (e.g., saved or discarded), error conditions (e.g., if timer isn't running), or response format. The reference to 'about' for examples doesn't compensate for these gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but includes a redundant meta-reference ('Use about...') that doesn't add value for tool selection. The first sentence is clear, but the second sentence is unnecessary clutter. It could be more front-loaded by omitting the about reference.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It doesn't explain what the tool returns, error handling, or side effects. For a tool that modifies state, more context is needed to ensure safe and correct usage by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the single parameter 'id' documented as 'Time entry ID'. The description adds no parameter-specific information beyond what's in the schema, such as format examples or where to obtain the ID. This meets the baseline of 3 since the schema adequately covers the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Stop') and resource ('a running time entry timer'), making the purpose immediately understandable. It distinguishes from siblings like 'harvest_restart_timer' by specifying 'stop' versus 'restart', though it doesn't explicitly contrast with other time entry tools like 'harvest_update_time_entry'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions using 'about' for workflow details, but this is a meta-reference rather than practical usage advice. There's no indication of prerequisites (e.g., only works on running timers) or when to choose this over other time entry operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/standardbeagle/harvest-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server