How to integrate Harvest MCP with CrewAI

This guide walks you through connecting Harvest to CrewAI 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 CrewAI 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 CrewAI 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 CrewAI 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 a Composio API key and configure your Harvest connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Harvest
  • Build a conversational loop where your agent can execute Harvest operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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 step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Harvest connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Harvest via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Harvest MCP URL
6

Create a Composio Tool Router session for Harvest

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["harvest"])

url = session.mcp.url
What's happening:
  • You create a Harvest only session through Composio
  • Composio returns an MCP HTTP URL that exposes Harvest tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Harvest and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["harvest"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Harvest through Composio's Tool Router. The agent can perform Harvest operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
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. CrewAI 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