How do I connect my Heroku account?

You subscribe to the MCP on Vinkius and enter your Heroku API Key. Once connected, your AI client can immediately start interacting with your Heroku account.

Which AI clients can I use with this MCP?

You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

Is it safe to view my environment variables through the AI?

The MCP allows your agent to retrieve decrypted config vars. This is useful for debugging, but you should manage access to your AI client carefully.

Can I restart just one specific worker?

Yes, you can use the restart_specific_dyno capability to reboot a single instance without affecting the rest of your application.

What happens if I use the delete_app capability?

The delete_app capability is highly destructive. It will permanently wipe the application and all its associated data from Heroku.

Can I see the status of my dynos through my agent?

Yes. Use the list_dynos capability to see the real-time status of each container process (e.g. web.1, worker.1). You'll know exactly if a dyno is up, crashed, starting, or idle.

How do I check my application's environment variables?

The list_config_vars capability allows your agent to dump the full dictionary of environment variables injected into your dynos, including sensitive keys like DATABASE_URL or API tokens.

Can my agent restart a specific hung worker without affecting the web traffic?

Absolutely. Use the restart_specific_dyno capability to reboot a single instance (e.g. worker.2). This is perfect for unsticking hung asynchronous queue workers without impacting your primary frontend traffic.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Heroku Paas to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run and monitor your Heroku infrastructure through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Heroku.

01
Create app
Provisions a new structural App container on the Heroku platform.
02
Delete app
Permanently removes an active App from Heroku. This is a destructive action that immediately stops all traffic routing.
03
List addons
Retrieves all third-party platform add-ons currently mapped to your application.
04
List apps
Shows all standard applications currently hosted on your Heroku account.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Heroku.

05
List dynos
Lists all containerized dynos in an app and tracks whether they are up, crashed, idle, or starting.
06
List config vars
Dumps decrypted application environment variables like database URLs and API keys.
07
Restart specific dyno
Reboots a single, isolated dyno instance to unstick specific workers without affecting web traffic.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Heroku.

08
Restart all dynos
Triggers a hard reboot for every container tied to a specific application to resolve memory leaks or stalled processes.
09
Toggle maintenance mode
Switches an application's maintenance mode on or off to block inbound requests during sensitive operations.
10
Get app info
Fetches runtime constraints, framework details, routing URLs, and regional datacenter placement for an app.

Real work

What teams actually run

Resolving Memory Leaks

Tell your agent to restart all dynos when a Node.js or Ruby runtime starts stalling.

Database Migrations

Enable maintenance mode via the AI before running complex sequential migrations.

Worker Troubleshooting

Reboot a single hung worker dyno without interrupting your main web traffic.

Environment Debugging

Quickly verify that the correct DATABASE_URL or API keys are set in your config vars.

Automate a task

Put Heroku to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Heroku works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Heroku to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

907ms average. Fast in production.

Heroku is checked daily against the live service.

Daily averagePeak 1107ms

Oct 3Today

Fastest day: 663ms
Slowest day: 1107ms
14-day trend: Stable-3%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Heroku, so you can see the experience inside your AI.

It does not authenticate your account with Heroku. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Heroku Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_HWnMOgL2zYPCutqVNumPjbm95CPIrkddpZrkVKOV/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Heroku capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "heroku-paas-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_HWnMOgL2zYPCutqVNumPjbm95CPIrkddpZrkVKOV/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Heroku in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Heroku owners hand off.

This MCP is built for engineers who want to manage cloud infrastructure without leaving their development environment.

01
DevOps Engineers
Monitor dyno health and execute cluster reboots via chat.
02
Backend Developers
Check environment variables and add-on statuses directly from an IDE.
03
System Admins
Manage maintenance windows and application lifecycles across regions.

FAQ

Questions Heroku owners ask.

01
How do I connect my Heroku account?
You subscribe to the MCP on Vinkius and enter your Heroku API Key. Once connected, your AI client can immediately start interacting with your Heroku account.
02
Which AI clients can I use with this MCP?
You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.
03
Is it safe to view my environment variables through the AI?
The MCP allows your agent to retrieve decrypted config vars. This is useful for debugging, but you should manage access to your AI client carefully.
04
Can I restart just one specific worker?
Yes, you can use the restart_specific_dyno capability to reboot a single instance without affecting the rest of your application.
05
What happens if I use the delete_app capability?
The delete_app capability is highly destructive. It will permanently wipe the application and all its associated data from Heroku.
06
Can I see the status of my dynos through my agent?
Yes. Use the list_dynos capability to see the real-time status of each container process (e.g. web.1, worker.1). You'll know exactly if a dyno is up, crashed, starting, or idle.
07
How do I check my application's environment variables?
The list_config_vars capability allows your agent to dump the full dictionary of environment variables injected into your dynos, including sensitive keys like DATABASE_URL or API tokens.
08
Can my agent restart a specific hung worker without affecting the web traffic?
Absolutely. Use the restart_specific_dyno capability to reboot a single instance (e.g. worker.2). This is perfect for unsticking hung asynchronous queue workers without impacting your primary frontend traffic.

Explore

More in Industry Titans

Connect Heroku to Claude, Cursor, ChatGPT & more

Your AI does the work. We keep it safe and sound.

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-04

Create app

Delete app

List addons

List apps

05-07

List dynos

List config vars

Restart specific dyno

08-10

Restart all dynos

Toggle maintenance mode

Get app info

What teams actually run

Resolving Memory Leaks

Database Migrations

Worker Troubleshooting

Environment Debugging

Building your own app? The connector is yours to use.

Heroku Connector

Claude Desktop

DevOps Engineers

Backend Developers

System Admins

How do I connect my Heroku account?

Which AI clients can I use with this MCP?

Is it safe to view my environment variables through the AI?

Can I restart just one specific worker?

What happens if I use the delete_app capability?

Can I see the status of my dynos through my agent?

How do I check my application's environment variables?

Can my agent restart a specific hung worker without affecting the web traffic?

Clever Cloud (Developer PaaS API) AI Connector

Gridscale (IaaS & PaaS Cloud Hosting API) AI Connector

Flightcontrol (AWS PaaS Deployments) AI Connector

JD Cloud Infrastructure AI Connector

Suggestions

Civo (Cloud-native Kubernetes Cloud Provider API) AI Connector

Zeabur (PaaS Deployment) AI Connector

Apple App Store AI Connector

Cloudify AI Connector