How to integrate Harvest MCP with Claude Agent SDK

This guide walks you through connecting Harvest to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Harvest agent that can create a new client for acme corp, log an expense for project 'website redesign', generate an invoice for hours worked this week through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Harvest account through Composio's Harvest MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Harvest logoHarvest
Oauth2

Harvest is a time-tracking and invoicing platform for teams and freelancers. It helps you log billable hours, manage projects, and streamline payments.

57 Tools

Introduction

This guide walks you through connecting Harvest to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Harvest agent that can create a new client for acme corp, log an expense for project 'website redesign', generate an invoice for hours worked this week through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Harvest account through Composio's Harvest MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Harvest with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Harvest
  • Configure an AI agent that can use Harvest as a tool
  • Run a live chat session where you can ask the agent to perform Harvest operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Harvest MCP server, and what's possible with it?

The Harvest MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Harvest account. It provides structured and secure access to your time-tracking, invoicing, and project management data, so your agent can create clients, log expenses, send invoices, record payments, and manage estimates automatically on your behalf.

  • Client and contact management: Seamlessly create new clients and add contacts to keep your client list up to date without manual entry.
  • Estimate creation and communication: Automatically generate new estimates, categorize line items, and send estimate messages or updates to clients.
  • Expense tracking automation: Log new expense entries against projects, ensuring accurate financial records and effortless cost tracking.
  • Streamlined invoicing and payments: Create professional invoices, categorize invoice items, send invoice notifications, and record payments as soon as they happen.
  • Project financial workflow optimization: Let your agent handle the full cycle—from creating clients to sending invoices and tracking payments—saving your team valuable time and reducing errors.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Harvest account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Harvest functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Harvest
  const session = await composio.create(USER_ID, {
    toolkits: ['harvest'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Harvest
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Harvest tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Harvest
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Harvest and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['harvest']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Harvest tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Harvest through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Harvest action and event your agent gets out of the box.

Create Client

Tool to create a new client.

Create Client Contact

Tool to create a new client contact.

Create Estimate

Tool to create a new estimate.

Create Estimate Item Category

Tool to create a new estimate item category in Harvest.

Create Estimate Message

Tool to create a new message for an estimate.

Create Expense

Tool to create a new expense entry.

Create Invoice

Tool to create a new invoice.

Create Invoice Item Category

Tool to create a new invoice item category.

Create Invoice Message

Creates a new message for an invoice in Harvest.

Create Invoice Payment

Tool to create a new payment on an invoice.

Create Project

Create a new project in Harvest.

Create Task

Creates a new task in Harvest.

Create Time Entry

Tool to create a new time entry.

Create User

Creates a new user in Harvest and sends an invitation email to the specified address.

Delete Client

Tool to delete a client.

Delete Client Contact

Permanently deletes a client contact from Harvest.

Delete Estimate

Tool to delete an estimate.

Delete Estimate Message

Tool to delete an estimate message.

Delete Invoice

Delete an invoice from Harvest.

Delete Invoice Item Category

Tool to delete an invoice item category from Harvest.

Delete Invoice Message

Tool to delete a message from an invoice.

Delete Invoice Payment

Tool to delete an invoice payment.

Delete Project

Tool to delete a project.

Delete Task

Tool to delete a task.

Delete Time Entry

Tool to delete a time entry.

Delete User

Tool to delete a user.

Get Client

Retrieves a specific client by ID from Harvest.

Get Company Info

Retrieves detailed information about the company associated with the authenticated Harvest account.

Get Estimate

Tool to retrieve a specific estimate by ID.

Get Invoice

Tool to retrieve a specific invoice by ID.

Get Project

Tool to retrieve a specific Harvest project by ID.

Get Task

Tool to retrieve a specific task by ID.

Get Time Entry

Tool to retrieve a single time entry by ID.

Get User

Tool to retrieve a specific user by ID.

List Client Contacts

Tool to list client contacts.

List Clients

Tool to list clients.

List Estimate Messages

Lists all messages associated with a specific estimate in Harvest.

List Expense Categories

Tool to list expense categories.

List Invoice Item Categories

Tool to retrieve invoice item categories.

List Invoice Messages

Tool to list messages associated with a given invoice.

List Invoice Payments

List all payments recorded for a specific invoice.

List Invoices

Tool to list invoices.

List projects

Tool to list projects.

List Tasks

Tool to list tasks.

List Time Entries

Tool to retrieve a list of time entries.

List Users

Tool to list users.

Update Client

Tool to update an existing client.

Update Client Contact

Tool to update a client contact.

Update Company Info

Updates company time tracking settings in Harvest.

Update Estimate

Tool to update an existing estimate.

Update Estimate Item Category

Updates an existing estimate item category's name in Harvest.

Update Expense

Tool to update an existing expense.

Update Invoice

Tool to update an existing invoice.

Update Project

Tool to update an existing project.

Update Task

Tool to update an existing task.

Update Time Entry

Tool to update an existing time entry.

Update User

Tool to update an existing user.

FAQ

Frequently asked questions

With a standalone Harvest MCP server, the agents and LLMs can only access a fixed set of Harvest tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Harvest and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Harvest tools.

Yes, absolutely. You can configure which Harvest scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Harvest data and credentials are handled as safely as possible.

Start with Harvest.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Harvest tool your agent needs.Free to start.

Start building