Bragproof

← Reports

@heroku/mcp-server

Starts with no setup1.2.14npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing

33tools listed
0hosts contacted
0files written
0.2 sto start
139dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @heroku/mcp-server@1.2.14

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 5 returned a result.

list_appsReturned a result under 0.1 s · 160 characters
list_private_spacesReturned a result under 0.1 s · 160 characters
list_teamsReturned a result under 0.1 s · 160 characters
list_addonsReturned a result under 0.1 s · 160 characters
list_addon_servicesReturned a result under 0.1 s · 160 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

list_apps all, personal, space, team
List Heroku apps: owned, collaborator access, team/space filtering
get_app_info app, json
Get app details: config, dynos, addons, access, domains
create_app app, region, space, team
Create app: custom name, region (US/EU), team, private space
rename_app app, newName
Rename app: validate and update app name
maintenance_on app
Enable maintenance mode and redirect traffic for a Heroku app
28 more tools
maintenance_off app
Disable maintenance mode and restore normal app operations
get_app_logs app, dynoName, source, processType
App logs: monitor/debug/filter by dyno/process/source
list_private_spaces json
Lists Heroku Private Spaces with CIDR blocks, regions, compliance and capacity details. JSON output supported.
list_teams json
Lists accessible Heroku Teams. Use for: viewing teams, checking membership, getting team metadata, and verifying access. JSON output available.
list_addons all, app
List add-ons: all apps or specific app, detailed metadata
get_addon_info addon, app
Get add-on details: plan, state, billing
create_addon app, as, name, serviceAndPlan
Create add-on: specify service, plan, custom names
list_addon_services json
List available add-on services and features
list_addon_plans service, json
List service plans: features, pricing, availability
pg_psql command, file, credential, app, database
Execute SQL queries: analyze, debug, modify schema, manage data
pg_info app, database
View database status: config, metrics, resources, health
pg_ps app, verbose, database
Monitor active queries: progress, resources, performance
pg_locks app, truncate, database
Analyze locks: blocked queries, deadlocks, concurrency
pg_outliers app, num, reset, truncate, database
Find resource-heavy queries: performance, patterns, optimization
pg_credentials app, database
Manage access: credentials, permissions, security, monitoring
pg_kill app, pid, force, database
Stop processes: stuck queries, blocking transactions, runaway operations
pg_maintenance app, database
Track maintenance: windows, schedules, progress, planning
pg_backups app
Manage backups: schedules, status, verification, recovery
pg_upgrade app, version, confirm, database
Upgrade PostgreSQL: version migration, compatibility, safety
ps_list app, json
List and monitor Heroku app dynos. View running dynos, check status/health, monitor process states, verify configurations.
ps_scale app, dyno
Scale Heroku app dynos. Adjust quantities, change sizes, view formation details, manage resources.
ps_restart app, dyno-name, process-type
Restart Heroku app processes. Restart specific dynos, process types, or all dynos. Reset dyno states selectively.
pipelines_create name, stage, app, team
Creates new Heroku deployment pipeline with configurable stages, apps, and team settings
pipelines_promote app, to
Promotes apps between pipeline stages with configurable target applications
pipelines_list json
Lists accessible Heroku pipelines with ownership and configuration details
pipelines_info pipeline, json
Displays detailed pipeline configuration, stages, and connected applications
deploy_to_heroku name, rootUri, tarballUri, teamId, spaceId, internalRouting, env, appJson
Use for all deployments. Deploys new/existing apps, with or without teams/spaces, and env vars to Heroku. Ask for app name if missing. Requires valid app.json via appJson param.
deploy_one_off_dyno name, command, sources, size, timeToLive, env
Run code/commands in Heroku one-off dyno with network and filesystem access.

Requirements:
- Show command output
- Use app_info for buildpack detection
- Support shell setup commands
- Use stdout/stderr

Features:
- Network/filesystem access
- Environment variables
- File operations
- Temp directory handling

Usage:
1. Use Heroku runtime
2. Proper syntax/imports
3. Organized code structure
4. Package management:
   - Define dependencies
   - Minimize external deps
   - Prefer native modules

Example package.json:
```json
{
  "type": "module",
  "dependencies": {
    "axios": "^1.6.0"
  }
}
```

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=20
Sourcegithub.com/heroku/heroku-mcp-server
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-QPZXPu8iFD1w+Gy5RVAgLkPnXuUJFH1Yx4awbRzI8F3TsrLwkQ2R0EX/yFKmUSMJtEoIodiZmWyFEYf3wdz1XA==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@heroku/mcp-server.svg)](https://bragproof.smaverk.com/r/%40heroku/mcp-server)

New version out? Ask for a fresh report.