MCP Heroku Server
Related Servers
Alternatives to MCP Heroku Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables 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.5811 npmMIT
- AlicenseBqualityDmaintenanceEnables 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.186 npm3MIT

Hellō Admin MCP Serverofficial
AlicenseAqualityDmaintenanceEnables 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.1198 npm4MIT
Roar AI MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables 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
Lizard MCPofficial
AlicenseAqualityBmaintenanceRun code in Lizard Sandboxes on Lizard (lizard.build). Provides 89 MCP tools, including 17 sandbox tools for commands, files, pause/resume, snapshots, forks and HTTPS ports, plus app, database and Git tools. Connect over Streamable HTTP with OAuth or your own API key. Cloud usage is billed; see lizard.build/pricing.893MIT- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to deploy and manage compatible web apps, isolated Postgres databases, and project file storage, while inspecting build logs, runtime errors, and usage through an OAuth-authenticated remote MCP connection.MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.