Connect an AI app
The HeadHoncho MCP server is at https://api.headhoncho.app/mcp. It speaks MCP over Streamable HTTP and answers JSON only. It offers the same 16 endpoints as tools, with the same names and the same arguments as the REST API, so what one can do the other can do.
Claude.ai and ChatGPT
Open the connector settings in the app, add a custom connector, and paste https://api.headhoncho.app/mcp. The app sends you to HeadHoncho's own page. There you choose which companies the app reaches, its access for each area, and whether personal details are hidden, then approve. No key is copied or pasted.
Claude Code
Add the server with a key from API keys:
claude mcp add --transport http headhoncho https://api.headhoncho.app/mcp \
--header "Authorization: Bearer hh_live_..."Cursor
Put this in .cursor/mcp.json:
{
"mcpServers": {
"headhoncho": {
"url": "https://api.headhoncho.app/mcp",
"headers": {
"Authorization": "Bearer hh_live_..."
}
}
}
}The tools
Each tool is documented on its own page, with its arguments, its answer and an example prompt on the "Your AI" tab. A tool tells the app whether it only reads, whether it can destroy anything (none can), and whether it is safe to repeat (all are).
| Tool | Group | Needs | Effect |
|---|---|---|---|
| `whoami` | Account | any key | Reads only |
| `list_jobs` | Jobs | read on Jobs | Reads only |
| `get_job` | Jobs | read on Jobs | Reads only |
| `get_job_history` | Jobs | read on Jobs | Reads only |
| `create_job` | Job commands | do on Jobs | Changes a job |
| `update_job` | Job commands | do on Jobs | Changes a job |
| `change_job_status` | Job commands | do on Jobs | Changes a job |
| `assign_worker` | Job commands | do on Jobs | Changes a job |
| `unassign_worker` | Job commands | do on Jobs | Changes a job |
| `add_job_note` | Job commands | do on Jobs | Changes a job |
| `list_tables` | Raw data | read on Raw data | Reads only |
| `read_table` | Raw data | read on Raw data | Reads only |
| `export_table` | Raw data | read on Raw data | Reads only |
| `get_job_conversion` | Click IDs and conversions | read on Click IDs and conversions | Reads only |
| `get_click_id_report` | Click IDs and conversions | read on Click IDs and conversions | Reads only |
| `export_click_id_report` | Click IDs and conversions | read on Click IDs and conversions | Reads only |
Downloads come back as a link
Export table and Export click id report return a file. Over MCP the answer is a one-time download link that works for five minutes, so the file never passes through the AI. Open the link yourself, or have your own code fetch it.
Who did it
When an AI app changes a job, the job's history records it as "Claude, for" and the name of the person who approved it, for example "Claude, for Ariel T.". Get job history returns that name in by. Rate limits are the same as for the REST API; see errors and rate limits.
To understand what the tools do before you let an app use them, start with the model. Keys are on API keys.