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 Mastra AI 10 tools — connect in under 2 minutes

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

docs.mastra.ai/docs/agents/mcp-tools

Built by Vinkius GDPR 10 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Heroku (PaaS) through the Vinkius and Mastra agents discover all tools automatically — type-safe, streaming-ready, and deployable anywhere Node.js runs.

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.

typescript

import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token — get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "heroku-paas": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Heroku (PaaS) Agent",
    instructions:
      "You help users interact with Heroku (PaaS) " +
      "using 10 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Heroku (PaaS)?"
  );
  console.log(result.text);
}

main();

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.

Mastra's agent abstraction provides a clean separation between LLM logic and Heroku (PaaS) tool infrastructure. Connect 10 tools through the Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution — deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

Follow these steps to integrate the Heroku (PaaS) MCP Server with Mastra AI.

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.ts and run with npx tsx agent.ts

Explore tools

Mastra discovers 10 tools from Heroku (PaaS) via MCP

Why Use Mastra AI with the Heroku (PaaS) MCP Server

Mastra AI provides unique advantages when paired with Heroku (PaaS) through the Model Context Protocol.

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure — add Heroku (PaaS) without touching business code

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

TypeScript-native: full type inference for every Heroku (PaaS) tool response with IDE autocomplete and compile-time checks

One-command deployment to any Node.js host — Vercel, Railway, Fly.io, or your own infrastructure

Heroku (PaaS) + Mastra AI Use Cases

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

Automated workflows: build multi-step agents that query Heroku (PaaS), process results, and trigger downstream actions in a typed pipeline

SaaS integrations: embed Heroku (PaaS) as a first-class tool in your product's AI features with Mastra's clean agent API

Background jobs: schedule Mastra agents to query Heroku (PaaS) on a cron and store results in your database automatically

Multi-agent systems: create specialist agents that collaborate using Heroku (PaaS) tools alongside other MCP servers

Heroku (PaaS) MCP Tools for Mastra AI (10)

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