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 VS Code Copilot 10 tools — connect in under 2 minutes

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

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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": {
      "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.

GitHub Copilot Agent mode brings Heroku (PaaS) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Heroku (PaaS) MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Heroku (PaaS)

Ask Copilot: "Using Heroku (PaaS), help me..." — 10 tools available

Why Use VS Code Copilot with the Heroku (PaaS) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Heroku (PaaS) through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Heroku (PaaS) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Heroku (PaaS) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Heroku (PaaS) MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Heroku (PaaS) to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Heroku (PaaS) to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Heroku (PaaS) + VS Code Copilot FAQ

Common questions about integrating Heroku (PaaS) MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.