Skip to main content
Glama

☁️ MCP Heroku Server

npm version License: MIT MCP

A complete Heroku management server for the Model Context Protocol (MCP). Provides comprehensive Heroku app management through the Heroku Platform API for AI assistants like Claude.

✨ Features

  • πŸ“‹ App Management - List, view, and manage your Heroku applications

  • πŸš€ Deployment History - View releases and deployment timeline

  • πŸ“Š Dyno Operations - Scale, restart, and monitor dynos

  • πŸ“ Log Access - Stream and filter application logs

  • πŸ”§ Configuration - Manage environment variables (config vars)

  • πŸ“¦ Add-on Management - List and monitor add-ons (databases, caches, etc.)

  • πŸ”’ Secure - Uses your Heroku API key with proper authentication

Related MCP server: Hellō Admin MCP Server

πŸ“‹ Prerequisites

  • Heroku CLI (optional, for generating API keys)

  • Node.js 16+ for running the MCP server

  • Heroku API Key - Get from Dashboard Account Settings

πŸš€ Quick Start

HEROKU_API_KEY=your-api-key npx @artik0din/mcp-heroku

Install globally

npm install -g @artik0din/mcp-heroku
export HEROKU_API_KEY=your-api-key
mcp-heroku

πŸ”§ Environment Variables

Set your Heroku API key:

Option 1: Environment Variable

export HEROKU_API_KEY=your-heroku-api-key

Option 2: .env file

cp .env.example .env
# Edit .env and add your HEROKU_API_KEY

Getting Your API Key

  1. Visit Heroku Dashboard Account Settings

  2. Scroll to "API Key" section

  3. Click "Reveal" to show your key

  4. Or use CLI: heroku auth:token

πŸ”§ MCP Client Setup

Add this server to your MCP client configuration:

Claude Desktop Configuration

{
  "mcpServers": {
    "heroku": {
      "command": "npx",
      "args": ["@artik0din/mcp-heroku"],
      "env": {
        "HEROKU_API_KEY": "your-heroku-api-key-here"
      }
    }
  }
}

Other MCP Clients

{
  "name": "heroku",
  "command": "npx",
  "args": ["@artik0din/mcp-heroku"],
  "env": {
    "HEROKU_API_KEY": "your-heroku-api-key-here"
  }
}

πŸ“š Available Tools

App Management

  • heroku_list_apps - List all your Heroku apps

    • team (string, optional) - Filter apps by team name

  • heroku_get_app - Get detailed app information

    • appName (string, required) - Name of the Heroku app

Deployment & Releases

  • heroku_list_releases - View deployment history

    • appName (string, required) - Name of the Heroku app

    • limit (number) - Max releases to return (default: 10)

Dyno Management

  • heroku_restart - Restart app dynos

    • appName (string, required) - Name of the Heroku app

    • dyno (string, optional) - Specific dyno (e.g., "web.1"), or omit for all

  • heroku_scale - Scale dynos up or down

    • appName (string, required) - Name of the Heroku app

    • dyno (string, required) - Dyno type (e.g., "web", "worker")

    • quantity (number, required) - Number of dynos to run

    • size (string, optional) - Dyno size (eco, basic, standard-1x, etc.)

Logs & Monitoring

  • heroku_get_logs - Retrieve application logs

    • appName (string, required) - Name of the Heroku app

    • lines (number) - Number of log lines (default: 100)

    • dyno (string, optional) - Filter by dyno (e.g., "web.1")

    • source (string, optional) - Filter by source ("app" or "heroku")

Add-ons

  • heroku_list_addons - List attached add-ons

    • appName (string, required) - Name of the Heroku app

Configuration

  • heroku_config_vars - Manage environment variables

    • appName (string, required) - Name of the Heroku app

    • set (boolean) - Set to true to modify (default: false, just lists)

    • key (string) - Config var key name

    • value (string) - Config var value (use with set=true)

πŸ’‘ Usage Examples

List all apps

// Use the heroku_list_apps tool
// Returns array of apps with basic info

Scale web dynos

// Use heroku_scale tool with:
// appName: "my-app"
// dyno: "web"
// quantity: 2
// size: "standard-1x"

Get recent logs

// Use heroku_get_logs tool with:
// appName: "my-app" 
// lines: 50
// source: "app"

Set environment variable

// Use heroku_config_vars tool with:
// appName: "my-app"
// set: true
// key: "DATABASE_URL"
// value: "postgres://..."

πŸ”’ Security

This server uses the Heroku Platform API securely:

  • API key is read from environment variables only

  • No credential storage or caching

  • All requests use HTTPS

  • Sensitive config vars are masked in responses

  • Uses official Heroku API endpoints

πŸ› οΈ Development

# Clone the repository
git clone https://github.com/artik0din/mcp-heroku.git
cd mcp-heroku

# Install dependencies
npm install

# Set environment variable
export HEROKU_API_KEY=your-key

# Build and run
npm run build
npm start

# Development mode
npm run dev

πŸ“ License

MIT License - see LICENSE file for details.

🀝 Contributing

Contributions welcome! Please feel free to submit a Pull Request.

Available Tools

8 tools
heroku_config_varsC

Get or set config vars (environment variables) for a Heroku app.

Inputs: appName (required), set, key, value.

heroku_get_appC

Get detailed information about a Heroku app including dynos and formation.

Inputs: appName (required).

heroku_get_logsC

Get recent logs from a Heroku app. Can filter by dyno or source.

Inputs: appName (required), lines, dyno, source.

heroku_list_addonsA

List all add-ons attached to a Heroku app (databases, caches, etc.)

Inputs: appName (required).

heroku_list_appsB

List all Heroku apps. Optionally filter by team.

Inputs: team.

heroku_list_releasesC

List releases for a Heroku app. Shows deployment history.

Inputs: appName (required), limit.

heroku_restartB

Restart dynos for a Heroku app. Can restart all dynos or a specific one.

Inputs: appName (required), dyno.

heroku_scaleC

Scale dynos for a Heroku app. Change the number of running dynos.

Inputs: appName (required), dyno (required), quantity (required), size.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific Heroku operations: config vars, app details, logs, add-ons, app listing, releases, restarting, and scaling. There is no overlap in functionality, and an agent can easily distinguish between them based on their specific resource and action combinations.

    Naming Consistency5/5

    All tool names follow a consistent 'heroku_' prefix with a verb_noun pattern (e.g., heroku_get_app, heroku_list_addons). The naming is uniform across all eight tools, using snake_case throughout, making it predictable and easy to understand.

    Tool Count5/5

    With 8 tools, this server is well-scoped for managing Heroku apps. Each tool serves a distinct and essential function in app management, covering monitoring, configuration, deployment, and scaling without being overly broad or too limited.

    Completeness4/5

    The tool set provides strong coverage for core Heroku app management, including monitoring (logs, releases), configuration (config vars, add-ons), and operations (restart, scale). A minor gap exists in CRUD operations for apps (e.g., create or delete an app), but agents can still handle most workflows effectively with the available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables management of Coolify instances to control applications, databases, and servers through the Model Context Protocol. It provides a comprehensive set of tools for deploying services and monitoring self-hosted infrastructure using natural language.
      18
      28 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to create and manage Hellō applications with full developer context, supporting app creation, updates, secret generation, and logo management through a single unified tool.
      1
      54 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to deploy and manage hosted apps from git repos, read logs, add Postgres databases and domains, manage API keys and budgets, and send requests to 200+ AI models. Connects over remote Streamable HTTP with OAuth sign-in, so users need no API keys, installs, or local server.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to deploy and roll back applications, read build and runtime logs, diagnose broken apps, and run commands inside containers. It also manages environment variables, PostgreSQL databases, domains, cron jobs, marketplace services, and backups on a PaaS platform, with safety annotations so clients can confirm destructive actions.
      58
      13 npm
      MIT