Harumi in ChatGPT and Claude
Connect Harumi to ChatGPT or Claude through the Harumi MCP server, then ask about your projects, runs, and dashboards in plain language.
Overview
The Harumi MCP server connects your Harumi account to a chat app — ChatGPT or Claude — over the Model Context Protocol. Once connected, you can ask about your work without leaving the chat: which projects you have, whether last night's run finished, why a run failed, what its dashboard shows. The answers come straight from Harumi.
Results render inline as Harumi-styled cards — the same status colours, branch badges, and monospace log you see in the platform — so a run list in the chat looks like a run list in Harumi, with an Open in Harumi link back to the platform.
The server lives at:
https://mcp.harumi.io/mcpConnect
Add Harumi as a connector
Add a custom connector (a remote MCP server) in your chat app and give it the URL above.
- Claude — add a custom connector from Claude's connector settings.
- ChatGPT — add a custom connector (an app) from ChatGPT's settings. Depending on your plan, ChatGPT may require developer mode to be turned on first.
No client ID or secret is needed: the chat app registers itself with the server automatically.
Sign in with your Harumi email
The chat app opens a Connect to Harumi page. Enter your Harumi email and press Send me a code, then enter the one-time code from your inbox and press Connect. This is the same emailed code you use to sign in to the platform and the CLI.
Ask something
Back in the chat, try:
- "List my Harumi projects."
- "Did the latest run of Demand Planning finish?"
- "Show me the last 200 lines of the log for that failed run."
- "Show the dashboard for the latest completed run."
No Harumi account yet?
The sign-in page can't create one. If your email isn't recognised, create an account on the Harumi platform first — see Account setup — then connect again.
What you can do
The server exposes one tool per area of Harumi, each with a few actions. The full list is in the tool reference.
| Area | Read | Change |
|---|---|---|
| Profile and organizations | your profile, your organizations, their members | your own profile fields |
| Projects | list projects with their latest run status, look one up by name | — |
| Runs | list runs, one run in full, its log, its dashboard | start a run, cancel a run |
| Repository | files, folders, branches, commits, file content, readiness, zip download | scratch branches and the files on them |
| Files | a project's files and their content | upload, remove |
| Data sources | list, details, run a read query | — |
| Schedules | list, details | add, update, remove |
| Secrets | secret names only | set, remove |
| Share links | list, details | add, update, remove, rotate, set or remove a password |
| Catalogue | kernel specs, project templates | — |
Long answers are trimmed, not dropped
Chat apps have limited room, so large results are capped and always say so:
- A run log returns the last 200 lines by default, with a notice and a link to the full log. Ask for more lines if you need them.
- File content over 20,000 characters is trimmed, with a link to the file in Harumi. An upload over that size is refused, with a link to finish it in the platform.
- A data source query returns at most 100 rows.
- A repository archive that's too large comes back as a download link.
Safety
Harumi has no permission scopes: the connection acts with your full account, the same as you do in the platform. The server is built around that.
- Changes that can't be undone ask first. Tools that can remove or overwrite something — cancelling a run, removing a file, schedule, secret, or share link, rotating a share link — are marked destructive, so your chat app asks you to confirm before it runs them.
- Some actions are never available. The server can't delete a project, an organization, or a data source; can't invite or remove people or change roles; can't promote a branch to live or write to the live branch; and can't touch billing.
- Secrets stay secret. The server lists secret names but never returns a secret's value, a data source password, or a share link's password.
- Your Harumi token never reaches the chat app. The server keeps your Harumi credentials encrypted on its side and gives the chat app its own token instead.
- A failed change says whether it happened. If Harumi refused a change, the answer says so and gives the reason. If the outcome is unclear (for example, a timeout), the answer says it doesn't know rather than suggesting a blind retry — so a run isn't started twice.
Staying connected
Your connection lasts 30 days and renews each time you use it. If it expires, or the server signs everyone out, your chat app asks you to connect again — nothing in your Harumi account is affected. To disconnect, remove the Harumi connector from your chat app.