Harvest + Grok Bot
Connect Harvest to Grok Bot
Prepare a grounded recorded-hours briefing
Read time entries with Grok Bot and Agent200. Prepare a recorded-hours briefing using the connected user’s own Harvest account.
On this page
Overview
Identify the selected time entry and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested read.
Start with one identified time entry. Preserve returned entry dates, hours, project and task IDs, and report totals actually returned; report missing data and keep the workflow read-only.
Provider reference: Harvest API.
- Connector
- Harvest
- Works with
- Grok Bot · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 6 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Harvest enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Harvest account. They approve access once, on Harvest's own page.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect Harvest to Grok Bot
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Harvest and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it. -
5
Step 5: Connect your Harvest account
The first time you ask Grok Bot for something in Harvest, Agent200 returns an authorization link. Open it and approve access on Harvest's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Review my Harvest time entries for the date range I provide. Use only the selected account and accessible records. Report hours by returned project and task, with any access gaps; do not change entries.
What should come back
- The selected time entry is identified.
- Only returned entry dates, hours, project and task IDs, and report totals actually returned are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected Harvest account, connected role, date range, project permission and pagination. A 403 or empty page does not prove the organization has no time entries.
Get your API key
Create a key in the Agent200 dashboard. It reaches Harvest and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Harvest to Grok Bot.
Goal: connect Harvest to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/harvest/framework/grok-bot/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Harvest is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands. 4. The first Harvest request returns an authorization link if the user has not connected Harvest yet: show it to them and continue once they have approved access on Harvest's own page. 5. Check it works with this request: "Review my Harvest time entries for the date range I provide. Use only the selected account and accessible records. Report hours by returned project and task, with any access gaps; do not change entries." What should come back: - The selected time entry is identified. - Only returned entry dates, hours, project and task IDs, and report totals actually returned are reported. - Access gaps and missing context are explicit; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Harvest, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/harvest/framework/grok-bot.md
Harvest tools Grok Bot can call
-
List time entries
Readharvest_list_time_entriesFind time entries within an explicit date, user or project scope.
-
Read a time entry
Readharvest_get_time_entryRetrieve one identified time entry and its recorded details.
-
List projects
Readharvest_list_projectsFind projects when the connected role has project-list access.
-
Read a project
Readharvest_get_projectRetrieve one identified project when the connected role permits it.
-
Project time report
Readharvest_time_report_by_projectRead recorded time grouped by project for an explicit date range.
-
Task time report
Readharvest_time_report_by_taskRead recorded time grouped by task for an explicit date range.
No tool matches that search.
How it works
-
01
You ask Grok Bot
In your own words, for something in Harvest.
-
02
Grok Bot picks a tool
It sees the Harvest tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Harvest connection, within the tools and scopes your project allows.
-
04
Grok Bot answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Harvest account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Harvest enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected Harvest account, connected role, date range, project permission and pagination. A 403 or empty page does not prove the organization has no time entries.
FAQ
How do I verify this result?
Compare the named time entry and returned entry dates, hours, project and task IDs, and report totals actually returned with the source. Treat missing information as missing, not as a fact.
