Heroku MCP connector
Connect Heroku to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client can look at and work on the apps, dynos, releases, and add-ons in your Heroku account, with every action logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which apps had a release this week and who deployed them?
Working in Heroku with Elaichi
-
Looked in Heroku
How to connect Heroku to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Heroku MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Heroku MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Heroku MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Heroku MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Heroku MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Heroku to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Heroku through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Heroku is logged.
-
Engineering
Check what shipped in the last release
Ask which release is live on an app, who deployed it, and what changed since the one before, without opening the Heroku dashboard mid-standup.
-
Platform
Find which app is running short on dynos
Ask for the dyno sizes and counts across every app in the account, then spot the one that has been running on a single dyno since the last restart.
-
Support
Confirm an app is healthy before replying
When a customer reports an outage, ask whether the app's dynos are up and when the last release went out, then answer the ticket with facts rather than guesses.
-
Product
See where each app sits in its pipeline
Ask which apps are in staging versus production for a pipeline, and whether the build the team is waiting on has been promoted yet.
-
Security
Review who can touch production apps
Pull the collaborators on every production app and compare them with the current team roster before a quarterly access review.
-
Finance
Tally add-on plans across the account
List the add-ons attached to each app and the plan each one is on, so the monthly Heroku bill can be matched to the apps that actually use them.
Try asking
- “Which apps had a release this week and who deployed them?”
- “Show the config vars on staging that differ from production.”
- “List add-ons attached to the billing app and their plans.”
What connecting Heroku gets you
5 screens from Elaichi, each doing one job for your Heroku account.
Ask Elaichi to work across your apps.
Which apps had a release this week and who deployed them?
Show the config vars on staging that differ from production.
List add-ons attached to the billing app and their plans.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your Heroku apps in plain words.
Get answers from live apps, dynos, releases and add-ons, not a stale dashboard export.
Copy the endpoint
AI apps
One endpoint puts Heroku in every AI client.
Claude, ChatGPT, Cursor and Microsoft Copilot all reach Heroku through one governed endpoint, no SDK, no shared key.
Toolboxes
Each team gets its own Heroku toolbox.
Scope what platform, support and finance can reach in Heroku, team by team.
Shared connections
Teammates use Heroku without touching a token.
One person connects Heroku, shares it with a team, and nobody else sees a credential.
Audit log
Every Heroku action names who did it.
When, who, what happened and which app, in an append-only log you can search.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Heroku digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch apps
Heroku
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Heroku
Queued
Workflows
Scheduled Heroku digests, approved by a person.
A schedule fetches releases, groups them by app, drafts a digest, and posts after approval.
Heroku health
Refreshed 4 minutes ago · every 15 minutes · from the apps collection
Apps
1,284 ↓ 12%
Dynos
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Apps created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Platform team 21%
Support 18%
Collections and dashboards
Heroku health numbers, computed with no model.
Releases over 14 days, dynos by team and add-on counts, refreshed on a schedule.
Why connect Heroku's MCP server through Elaichi
Heroku builds and runs this MCP server. Elaichi sits in front of it, so Heroku's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Heroku's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Heroku's tools at the same Elaichi address as every other connected app. Nobody adds Heroku's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Heroku sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Heroku's server. By default, a tool Heroku does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Heroku
Heroku builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Heroku team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Heroku
All three can connect Heroku to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Heroku tools | Allow or restrict single Heroku tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Heroku call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Questions, answered
How do I connect Heroku to Claude?
Connect Heroku in Elaichi first: pick Heroku from the catalog, a Heroku sign-in window opens, you approve, and the connection is ready. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint.
Does Heroku work with ChatGPT and Cursor as well as Claude?
Yes. Once Heroku is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Heroku once and every client sees it.
What can an AI agent actually do with my Heroku account?
It can work on the apps in your Heroku account: list apps and their dynos, read releases and config, check add-ons and pipelines, and make changes where your account allows. Exactly what is available depends on what your Heroku account has set up. Short, concrete asks such as "which apps had a release today" work better than long paragraphs.
Does connecting Heroku give the AI access to every app in the account?
No. The AI acts as the person who signed in to Heroku, so it sees only the apps and pipelines that person already has access to in Heroku. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Heroku itself grants that person.
Can I stop an agent from deleting or changing things in Heroku?
Yes. Restrictions in Elaichi apply per action, so you can allow reading apps, releases, and dynos while restricting anything that deletes an app, changes config, or scales dynos. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to a Heroku connection when someone leaves?
Offboarding that person in Elaichi ends their Heroku access through every client at once. A Heroku connection shared with a team keeps working for everyone else. Disconnecting Heroku once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in the same step.
Does the Heroku MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Heroku is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Heroku?
Yes. Both let Claude, ChatGPT or Cursor use Heroku. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Heroku call.
How is Elaichi different from Composio for Heroku?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Heroku: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Heroku in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot