Available

Harvest MCP server

Harvest is time-tracking and invoicing software for teams and freelancers, used to log billable hours and manage client billing. People teams rely on it to keep employee records accurate without manual double entry. Connect through Arc0 to use the actions your identity is allowed to call.

HR and recruitingPersonal access token and account IDMCP + RESTgetharvest.com
AUDIT LOG · HARVESTPOLICY: acme-support
09:41:07 · claude · u_8f2read
harvest.list_clients
List clients✓ allowed · 212ms
09:41:08 · claude · u_8f2read
harvest.get_me
Get me✓ allowed · 164ms
09:41:09 · claude · u_8f2write
harvest.create_time_entry
Create time entry✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
harvest.delete_time_entry
Delete time entry✕ blocked · policy: deny
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT
01 · USE CASES

Agent workflows for Harvest.

01

Get me

Use when finding the connected user ID before filtering time entries or comparing ownership before a write. Returns structural user fields without names or email; available without administrator permissions.

02

Get time entry

Use when inspecting a specific time entry or reconciling an uncertain write. Returns structural time and ownership fields without personal names or notes.

03

Create time entry

Use when logging positive hours for the connected user in a verified duration account. Start/end-time accounts may start a timer: if is_running is true, tell the user; do not retry. Reconcile uncertain writes with list/get before retrying; no deduplication is promised.

02 · ACTIONS

10 Harvest actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

7

Look things up, subject to your permissions.

  • harvest.get_me
    Get me

    Use when finding the connected user ID before filtering time entries or comparing ownership before a write. Returns structural user fields without names or email; available without administrator permissions.

  • harvest.get_time_entry
    Get time entry

    Use when inspecting a specific time entry or reconciling an uncertain write. Returns structural time and ownership fields without personal names or notes.

  • harvest.get_company
    Get company

    Use when checking whether this account tracks durations or start/end times before logging time. Requires administrator permissions; returns structural settings only.

  • harvest.list_time_entries
    List time entries

    Use when reviewing a date range up to 31 days or reconciling a write. Without user_id, admins see everyone and managers may see teammates. Use get_me for your own user_id. Pass next with unchanged filters for more.

  • harvest.list_projects
    List projects

    Use when finding project IDs for time tracking. Requires administrator or manager access to projects. Filter by client or active status and pass next with the same filters for another page.

  • harvest.list_task_assignments
    List task assignments

    Use when finding valid task IDs for a known project before logging time. Requires administrator or project manager access. Select task.id, not the assignment ID; pass next with the same project and filters for more.

  • harvest.list_clients
    List clients

    Use when finding client IDs to filter projects. Requires administrator or manager permission to manage clients. Returns names and currency without addresses or statement keys; pass next with unchanged filters for more.

write

2

Create and change things. Allow, or ask the user first.

  • harvest.create_time_entry
    Create time entry

    Use when logging positive hours for the connected user in a verified duration account. Start/end-time accounts may start a timer: if is_running is true, tell the user; do not retry. Reconcile uncertain writes with list/get before retrying; no deduplication is promised.

  • harvest.update_time_entry
    Update time entry

    Use when correcting hours or notes on a stopped duration entry. Admins/managers with permission can edit teammates: compare user.id with get_me and confirm authorization first. Send only changed fields. Read back uncertain results before retrying.

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • harvest.delete_time_entry
    Delete time entry

    Use when permanently deleting an authorized entry. Admins/managers with permission can delete teammates: compare user.id with get_me first. Confirm the ID; closed entries or archived assignments may refuse deletion. Read back uncertain results.

03 · POLICIES AND AUDIT

Control access to Harvest.

Connect the intended Harvest account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • harvest.create_time_entry: require approval
  • harvest.delete_time_entry: deny

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Harvest connects.

Connect Harvest using Personal access token and account ID. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
Personal access token and account ID
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use Harvest with your AI client.

Sign in to Arc0 and connect Harvest in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Harvest with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Harvest with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Harvest with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Harvest with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Harvest with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Harvest with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

Harvest and Arc0, answered.

Q01

Does Harvest work with Claude Desktop and Claude Code?

Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.

Q02

Can I use Harvest with OpenAI Codex, ChatGPT and Cursor?

Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.

Q03

Is this the official Harvest MCP server?

This is Arc0’s integration page, not a claim of an official Harvest server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Harvest for its own current MCP offerings.

Q04

Which Harvest actions are supported?

10 registry-defined actions: 7 read, 2 write and 1 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.

Q05

Which permissions does Harvest need?

Connect Harvest using Personal access token and account ID. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

Q06

Can I restrict writes in Harvest?

You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.

Q07

What does Harvest through Arc0 cost?

See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.

Get started

Plug Harvest into your agent.

Harvest MCP server: 10 actions including get me, get time entry, create time entry. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Harvest and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Harvest.