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

Yes. Use the `list_dynos` tool 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` tool 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` tool to reboot a single instance (e.g. worker.2). This is perfect for unsticking hung asynchronous queue workers without impacting your primary frontend traffic.

Heroku (PaaS) MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Name: Heroku (PaaS)
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Heroku (PaaS) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "heroku-paas": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Heroku (PaaS) MCP Server

Connect your Heroku account to any AI agent and take full control of your cloud-native application management and dyno orchestration through natural conversation.

Claude Desktop is the definitive way to connect Heroku (PaaS) to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

App Management — List all hosted applications, create new deployment boundaries, and fetch intricate runtime constraints and framework details directly from your agent
Dyno Orchestration — List individual containerized dynos, track their status (up, crashed, idle), and selectively reboot specific instances or entire clusters
Environment & Config — Audit decrypted application environment variables (Config Vars) and retrieve third-party platform add-ons like Postgres or Redis
Operational Control — Rapidly toggle maintenance mode to block inbound requests during migrations and perform hard reboots on stalled application clusters
Infrastructure Audit — Identify underlying executing stacks (e.g. heroku-24), regional datacenter placements (US/EU), and total slug size in memory

The Heroku (PaaS) MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Heroku (PaaS) to Claude Desktop via MCP

Follow these steps to integrate the Heroku (PaaS) MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Heroku (PaaS)

Look for the 🔌 icon in the chat — your 10 tools are now available

Why Use Claude Desktop with the Heroku (PaaS) MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Heroku (PaaS) through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Heroku (PaaS) + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Heroku (PaaS) MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Heroku (PaaS) MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Heroku (PaaS) to Claude Desktop via MCP:

create_app

Provision a fresh structural App container on Heroku

delete_app

Traffic routing instantly yields persistent 404/no web-dynos responses. Highly destructive. Permanently wipe an active App from Heroku servers

get_app_info

g. heroku-22, heroku-24). Confirms exact application routing URL mapping, total slug (code) size in memory, and regional datacenter placements (US or EU) verifying global latency strategies. Fetch intricate runtime constraints and framework details of an App

list_addons

Retrieve third-party Platform Add-ons mapping to an App

list_apps

Use this to discover App IDs, web URL designations, and git repository targets required to execute operational commands downstream. List all standard applications actively hosted on Heroku PaaS

list_config_vars

Retrieves highly confidential database tokens `DATABASE_URL`, SendGrid passwords, or OAuth keys. Dump decrypted Application Environment Variables

list_dynos

1, worker.1). Tracks exactly whether the dyno is "up", "crashed", "idle", or "starting" based on the internal slug runner engine's telemetry. List discrete containerized Dynos executing inside an App

restart_all_dynos

Often resolves ephemeral memory-leaks in Node.js or Ruby runtimes stalling standard request processing. Hard reboot all containers tied to an entire Application

restart_specific_dyno

Exceedingly useful for unsticking hung asynchronous queue workers without impacting active web traffic on the primary frontend replicas. Selectively reboot one isolated Dyno instance (e.g. worker.2)

toggle_maintenance_mode

Crucial for orchestrating complex sequential database migrations without encountering corrupted states from active sessions. Rapidly switch an Application's Maintenance Mode switch

Example Prompts for Heroku (PaaS) in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Heroku (PaaS) immediately.

"List all my Heroku apps"

"Restart all dynos for 'production-api'"

"What's the current maintenance mode status for the 'staging-web' app?"

Troubleshooting Heroku (PaaS) MCP Server with Claude Desktop

Common issues when connecting Heroku (PaaS) to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Heroku (PaaS) + Claude Desktop FAQ

Common questions about integrating Heroku (PaaS) MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.