{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-herokumcp-server","slug":"npm-herokumcp-server","name":"@heroku/mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@heroku/mcp-server","page_url":"https://unfragile.ai/npm-herokumcp-server","categories":["mcp-servers"],"tags":["heroku","mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-herokumcp-server__cap_0","uri":"capability://tool.use.integration.heroku.app.lifecycle.management.via.mcp.protocol","name":"heroku app lifecycle management via mcp protocol","description":"Exposes Heroku Platform API operations (create, deploy, scale, restart apps) through the Model Context Protocol, allowing LLM agents and Claude to directly invoke Heroku CLI-equivalent commands without shell execution. Uses MCP's tool-calling schema to map Heroku API endpoints to structured function definitions with parameter validation and response serialization.","intents":["I want my AI agent to deploy code to Heroku without manual intervention","I need Claude to manage app scaling and resource allocation based on monitoring data","I want to automate Heroku app lifecycle tasks (create, delete, restart) through natural language","I need to integrate Heroku operations into an agentic workflow without writing custom API clients"],"best_for":["DevOps engineers building AI-assisted deployment workflows","Solo developers automating Heroku app management through Claude","Teams integrating Heroku into LLM-powered CI/CD pipelines","Founders prototyping serverless app management with AI agents"],"limitations":["Requires valid Heroku API token with appropriate OAuth scopes — no built-in token refresh or rotation","MCP protocol overhead adds ~100-200ms per request vs direct REST calls","Limited to operations exposed by Heroku Platform API v3 — advanced features like private spaces require additional configuration","No built-in rate limiting — subject to Heroku API rate limits (1200 requests/hour per token)","Stateless design — no persistent session management or operation queuing across MCP invocations"],"requires":["Node.js 16+ (MCP server runtime)","Heroku API token (generated via `heroku auth:token` or OAuth)","MCP client implementation (Claude Desktop, custom agent framework, or compatible tool)","@heroku/mcp-server npm package installed"],"input_types":["structured JSON parameters (app name, dyno type, config vars)","natural language instructions (via Claude or LLM agent)","environment variable references (HEROKU_API_TOKEN)"],"output_types":["structured JSON responses (app metadata, deployment status, resource info)","operation confirmation messages","error details with Heroku API error codes"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-herokumcp-server__cap_1","uri":"capability://tool.use.integration.heroku.app.configuration.and.environment.variable.management","name":"heroku app configuration and environment variable management","description":"Allows reading, writing, and updating Heroku app config variables (environment variables) through MCP tool calls, with support for bulk operations and validation. Implements config var CRUD operations by wrapping Heroku's config endpoint, enabling agents to manage secrets, database URLs, and feature flags without direct API access.","intents":["I want Claude to update database connection strings when provisioning new add-ons","I need to rotate API keys and secrets across multiple Heroku apps via an agent","I want to enable/disable feature flags by updating config variables through natural language","I need to retrieve current environment configuration for debugging or auditing purposes"],"best_for":["Platform engineers managing configuration across multiple Heroku apps","DevOps teams automating secret rotation and config updates","Developers building self-service app configuration tools with AI","Teams needing audit trails of config changes via LLM-driven workflows"],"limitations":["No built-in encryption for sensitive values — config vars are base64-encoded in transit but stored plaintext in Heroku","Bulk config updates are not atomic — partial failures may leave apps in inconsistent state","No change history or rollback mechanism — requires external versioning to track config changes","Config var size limit of 32KB per variable enforced by Heroku platform","No support for config var inheritance or templating — each app requires explicit variable definitions"],"requires":["Heroku API token with 'read' and 'write' scopes for target apps","Valid Heroku app name or ID","MCP client with tool-calling support"],"input_types":["key-value pairs (config variable names and values)","JSON objects for bulk config updates","app identifiers (name or UUID)"],"output_types":["structured JSON with current config state","confirmation of config updates with timestamps","validation errors for invalid variable names or values"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-herokumcp-server__cap_2","uri":"capability://tool.use.integration.heroku.dyno.and.resource.scaling.via.agent.instructions","name":"heroku dyno and resource scaling via agent instructions","description":"Enables LLM agents to scale Heroku dynos (change dyno type, adjust process counts) through MCP tool calls with parameter validation. Maps natural language scaling requests to Heroku's dyno formation API, supporting both vertical scaling (dyno type changes) and horizontal scaling (process count adjustments) with real-time status feedback.","intents":["I want Claude to automatically scale up dynos when monitoring alerts indicate high load","I need to downscale to cheaper dyno types during off-peak hours to reduce costs","I want to adjust worker process counts based on queue depth reported by an agent","I need to scale multiple apps in parallel based on traffic patterns"],"best_for":["DevOps teams automating cost optimization through dynamic scaling","Startups building self-healing infrastructure with AI agents","Teams implementing auto-scaling policies driven by monitoring data","Solo developers managing resource costs through intelligent scaling"],"limitations":["Scaling operations are not instantaneous — dyno restarts typically take 10-30 seconds, during which app is briefly unavailable","No built-in cost estimation — agents must reference external pricing data to make cost-aware scaling decisions","Scaling down may cause data loss if apps maintain in-memory state — no automatic persistence layer","Heroku free/hobby dynos cannot be scaled to production types without app restart","No support for scheduled scaling — requires external scheduler to trigger scaling operations at specific times"],"requires":["Heroku API token with 'write' scope for dyno formation","Valid app name and process type (web, worker, etc.)","MCP client with tool-calling capability"],"input_types":["dyno type identifiers (standard-1x, standard-2x, performance-m, etc.)","process counts (integer for number of dynos)","app identifiers"],"output_types":["dyno formation status (current and target state)","scaling operation confirmation with estimated completion time","error details if scaling fails (e.g., insufficient account credits)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-herokumcp-server__cap_3","uri":"capability://tool.use.integration.heroku.app.deployment.and.release.management","name":"heroku app deployment and release management","description":"Exposes Heroku deployment operations (trigger builds, manage releases, view deployment history) through MCP tools, enabling agents to deploy code and manage release rollbacks. Integrates with Heroku's build and release APIs to provide deployment status tracking and release information without requiring direct git push or CLI commands.","intents":["I want Claude to deploy the latest code from a git branch to a Heroku app","I need to rollback to a previous release if deployment health checks fail","I want to view deployment history and release notes for auditing purposes","I need to trigger builds and monitor deployment progress through an agent"],"best_for":["Teams automating CI/CD pipelines with AI-driven deployment decisions","DevOps engineers building intelligent rollback mechanisms","Developers implementing self-service deployment workflows","Organizations requiring audit trails of deployments via LLM agents"],"limitations":["Requires Heroku git remote or GitHub integration — cannot deploy arbitrary code without prior setup","Build times vary (2-10 minutes) — agents must handle async operations and polling for completion","No built-in health check integration — rollback decisions must be made by external monitoring systems","Release history is limited to 250 most recent releases per app","Deployment failures may leave apps in intermediate states — requires manual intervention to recover"],"requires":["Heroku API token with 'write' scope for builds and releases","Git repository configured with Heroku remote or GitHub integration enabled","Valid app name and branch/commit reference","MCP client with async operation support"],"input_types":["git branch names or commit SHAs","app identifiers","release version numbers (for rollback operations)"],"output_types":["build status and logs","release information (version, timestamp, slug size)","deployment progress indicators","error details with build failure reasons"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-herokumcp-server__cap_4","uri":"capability://tool.use.integration.heroku.add.on.provisioning.and.lifecycle.management","name":"heroku add-on provisioning and lifecycle management","description":"Enables agents to provision, configure, and manage Heroku add-ons (databases, caching, monitoring services) through MCP tool calls. Implements add-on CRUD operations by wrapping Heroku's add-on API, supporting plan selection, attachment to apps, and deprovisioning with proper cleanup.","intents":["I want Claude to provision a PostgreSQL database when creating a new app","I need to upgrade a Redis cache plan based on memory usage metrics","I want to attach monitoring add-ons to multiple apps in parallel","I need to deprovision add-ons and clean up resources when shutting down apps"],"best_for":["Platform engineers automating infrastructure provisioning","Startups building self-service app creation workflows","Teams managing add-on lifecycle at scale","Developers implementing intelligent resource allocation"],"limitations":["Add-on provisioning is asynchronous — typically takes 30 seconds to 5 minutes, requires polling for completion","Plan upgrades may cause brief service interruptions — no zero-downtime upgrade option for most add-ons","Deprovisioning is destructive and irreversible — no built-in backup or recovery mechanism","Add-on availability varies by region — agents must validate region compatibility before provisioning","Billing integration is not exposed — cost calculations require external pricing data"],"requires":["Heroku API token with 'write' scope for add-ons","Valid app name","Add-on service identifier (e.g., heroku-postgresql, heroku-redis)","Plan identifier (e.g., standard-0, premium-2)"],"input_types":["add-on service names","plan identifiers","app identifiers","configuration options (region, backup settings, etc.)"],"output_types":["add-on provisioning status","connection strings and credentials","plan details and pricing information","attachment confirmation"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-herokumcp-server__cap_5","uri":"capability://search.retrieval.heroku.app.monitoring.and.log.retrieval.via.mcp","name":"heroku app monitoring and log retrieval via mcp","description":"Provides agents with access to Heroku app logs, metrics, and status information through MCP tool calls, enabling real-time monitoring and troubleshooting without dashboard access. Implements log streaming and metric queries by wrapping Heroku's log and metrics APIs, with filtering and time-range support.","intents":["I want Claude to retrieve recent error logs to diagnose app failures","I need to check dyno memory usage and CPU metrics to inform scaling decisions","I want to monitor app status and receive alerts when health checks fail","I need to retrieve logs for specific processes (web, worker) to debug issues"],"best_for":["DevOps teams building AI-assisted troubleshooting workflows","Developers debugging production issues through natural language queries","Teams implementing intelligent alerting based on log analysis","Solo developers monitoring apps without dashboard access"],"limitations":["Log retention is limited to 1500 lines per app — historical analysis requires external log aggregation","Metrics API has 1-minute granularity — fine-grained performance analysis requires external monitoring tools","Log streaming is not real-time through MCP — agents see batched logs with potential 30-60 second delay","No built-in log parsing or structured extraction — agents must parse text logs to extract meaningful data","Heroku Logs API rate limits apply (1200 requests/hour) — high-frequency monitoring may hit limits"],"requires":["Heroku API token with 'read' scope","Valid app name","MCP client with streaming or polling support"],"input_types":["app identifiers","time ranges (start/end timestamps)","process type filters (web, worker, etc.)","log source filters (app, system, etc.)"],"output_types":["log lines with timestamps and process information","dyno metrics (memory, CPU, load average)","app status (running, crashed, etc.)","error summaries and stack traces"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-herokumcp-server__cap_6","uri":"capability://tool.use.integration.heroku.app.creation.and.deletion.with.configuration","name":"heroku app creation and deletion with configuration","description":"Enables agents to create new Heroku apps with initial configuration (buildpack, region, stack) and delete apps through MCP tool calls. Implements app lifecycle operations by wrapping Heroku's app creation and deletion APIs, with support for specifying app name, region, and buildpack preferences.","intents":["I want Claude to create a new Heroku app with a specific buildpack and region","I need to provision multiple apps in parallel for testing or staging environments","I want to clean up old apps and free up resources when they're no longer needed","I need to create apps with specific configurations (stack version, region) based on requirements"],"best_for":["Platform teams automating app provisioning workflows","Startups building self-service app creation for users","DevOps engineers managing multi-app deployments","Teams implementing infrastructure-as-code with AI agents"],"limitations":["App creation is asynchronous — typically takes 5-10 seconds, requires polling for completion","App names must be globally unique across Heroku — agents must handle naming conflicts and retry logic","Deletion is irreversible — no built-in backup or recovery mechanism for deleted apps","Region availability varies by buildpack and add-on — agents must validate region compatibility","Initial configuration is limited to buildpack, region, and stack — advanced settings require post-creation API calls"],"requires":["Heroku API token with 'write' scope for app creation/deletion","Unique app name (or auto-generation strategy)","Valid region identifier (us, eu, etc.)","Valid buildpack identifier (heroku/ruby, heroku/python, etc.)"],"input_types":["app name (optional, auto-generated if not provided)","region identifier","buildpack identifier","stack identifier (heroku-20, heroku-22, etc.)"],"output_types":["app creation confirmation with app ID and URL","app configuration details (region, buildpack, stack)","deletion confirmation","error details if creation/deletion fails"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-herokumcp-server__cap_7","uri":"capability://tool.use.integration.heroku.team.and.collaborator.management","name":"heroku team and collaborator management","description":"Allows agents to manage team membership and collaborator access to Heroku apps through MCP tool calls, supporting role-based access control (owner, collaborator, member). Implements team operations by wrapping Heroku's team and app collaborator APIs, enabling agents to grant/revoke access and manage team structure.","intents":["I want Claude to grant a developer access to a specific app with collaborator role","I need to revoke access for team members who are leaving the organization","I want to manage team membership and assign roles based on responsibilities","I need to audit who has access to critical apps and update permissions"],"best_for":["Platform teams managing access control at scale","Organizations implementing least-privilege access policies","DevOps teams automating onboarding/offboarding workflows","Teams requiring audit trails of access changes"],"limitations":["Role-based access control is limited to owner, collaborator, and member — no fine-grained permission scoping","Access changes are immediate — no approval workflow or staged rollout mechanism","No built-in audit logging — access changes must be tracked externally","Team creation and deletion require account-level permissions — not all API tokens have these scopes","Collaborator removal is not reversible without re-adding — no soft-delete or grace period"],"requires":["Heroku API token with 'write' scope for team and collaborator management","Valid app name or team identifier","Email address of user to grant/revoke access","Role identifier (owner, collaborator, member)"],"input_types":["app identifiers","team identifiers","email addresses","role names (owner, collaborator, member)"],"output_types":["collaborator list with roles and permissions","access grant/revoke confirmation","team membership information","error details if access change fails"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":34,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+ (MCP server runtime)","Heroku API token (generated via `heroku auth:token` or OAuth)","MCP client implementation (Claude Desktop, custom agent framework, or compatible tool)","@heroku/mcp-server npm package installed","Heroku API token with 'read' and 'write' scopes for target apps","Valid Heroku app name or ID","MCP client with tool-calling support","Heroku API token with 'write' scope for dyno formation","Valid app name and process type (web, worker, etc.)","MCP client with tool-calling capability"],"failure_modes":["Requires valid Heroku API token with appropriate OAuth scopes — no built-in token refresh or rotation","MCP protocol overhead adds ~100-200ms per request vs direct REST calls","Limited to operations exposed by Heroku Platform API v3 — advanced features like private spaces require additional configuration","No built-in rate limiting — subject to Heroku API rate limits (1200 requests/hour per token)","Stateless design — no persistent session management or operation queuing across MCP invocations","No built-in encryption for sensitive values — config vars are base64-encoded in transit but stored plaintext in Heroku","Bulk config updates are not atomic — partial failures may leave apps in inconsistent state","No change history or rollback mechanism — requires external versioning to track config changes","Config var size limit of 32KB per variable enforced by Heroku platform","No support for config var inheritance or templating — each app requires explicit variable definitions","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.4143027610190178,"quality":0.26,"ecosystem":0.36,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:32.152Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":5895,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-herokumcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-herokumcp-server"}},"signature":"9iuwMydg1jTDN0r8aP5rk7LO+LgCj7t63KsWQf6i/JJfiXqpHthVz19kkzO8DlgJcFD8Nr24Qyd6Y0/DuD2SDQ==","signedAt":"2026-06-19T18:11:16.870Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-herokumcp-server","artifact":"https://unfragile.ai/npm-herokumcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-herokumcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}