Heroku Code Mcp

Name: Heroku Code Mcp
Author: dsouzaAnush

by dsouzaAnushcommunityv0.1.0

An MCP server for the Heroku Platform API that exposes three tools: auth status, search for Heroku operations, and execute a selected operation. It uses a compact code-mode flow to validate parameters and call Heroku API actions, with writes gated by dry-run confirmation and configuration flags.

From the registry: Search and execute Heroku Platform API operations

GitHub Repository Website

Install & configure

Prerequisites

required
Install Node.js and npm
Node.js and npm are required to run the server from GitHub via npx.
required
Install and authenticate the Heroku CLI
The README seeds authentication from the Heroku CLI. Run Heroku CLI login/auth first, then seed the token store for this MCP server.
```
$ heroku auth:whoami
```
https://devcenter.heroku.com/articles/heroku-cli
required
Seed MCP auth token store
Populate the server's encrypted token store from your Heroku CLI authentication before starting the MCP server.
```
$ npm run seed:token
```
required
Generate a token encryption key
Create a base64-encoded 32-byte key to use for TOKEN_ENCRYPTION_KEY_BASE64. The README refers to using the seed output key or a base64 32-byte key.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `heroku-code-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js and npm** — Node.js and npm are required to run the server from GitHub via npx.
- **Install and authenticate the Heroku CLI** — The README seeds authentication from the Heroku CLI. Run Heroku CLI login/auth first, then seed the token store for this MCP server. Run: `heroku auth:whoami` (https://devcenter.heroku.com/articles/heroku-cli)
- **Seed MCP auth token store** — Populate the server's encrypted token store from your Heroku CLI authentication before starting the MCP server. Run: `npm run seed:token`
- **Generate a token encryption key** — Create a base64-encoded 32-byte key to use for TOKEN_ENCRYPTION_KEY_BASE64. The README refers to using the seed output key or a base64 32-byte key.

Canonical MCP server config (HTTP transport):
- url: `http://127.0.0.1:<port>/mcp`
- headers:
  - `x-user-id`: `<user-id>`

Note: Preferred portable setup is to run the server separately and connect over HTTP. The README also shows a stdio bridge using mcp-remote, but the native server transport is streamable HTTP/HTTP. To run the server from GitHub before npm publication, use npx with env vars such as HOST, PORT, TOKEN_STORE_PATH, TOKEN_ENCRYPTION_KEY_BASE64, and optionally WRITE_CONFIRMATION_SECRET. Default examples use HOST=127.0.0.1, PORT=3000 or 3333, and x-user-id: default. Relevant server env vars mentioned in the README: TOKEN_STORE_PATH (required, path to encrypted token store), TOKEN_ENCRYPTION_KEY_BASE64 (required, base64 32-byte key), HOST (required for startup configuration), PORT (required for startup configuration), WRITE_CONFIRMATION_SECRET (optional, used in the GitHub npx example), ALLOW_WRITES (optional; required only if you want mutation operations enabled), REQUEST_TIMEOUT_MS (optional), MAX_RETRIES (optional), CATALOG_CACHE_PATH (optional), READ_CACHE_TTL_MS (optional), EXECUTE_MAX_BODY_BYTES (optional), EXECUTE_BODY_PREVIEW_CHARS (optional).

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Preferred portable setup is to run the server separately and connect over HTTP. The README also shows a stdio bridge using mcp-remote, but the native server transport is streamable HTTP/HTTP. To run the server from GitHub before npm publication, use npx with env vars such as HOST, PORT, TOKEN_STORE_PATH, TOKEN_ENCRYPTION_KEY_BASE64, and optionally WRITE_CONFIRMATION_SECRET. Default examples use HOST=127.0.0.1, PORT=3000 or 3333, and x-user-id: default. Relevant server env vars mentioned in the README: TOKEN_STORE_PATH (required, path to encrypted token store), TOKEN_ENCRYPTION_KEY_BASE64 (required, base64 32-byte key), HOST (required for startup configuration), PORT (required for startup configuration), WRITE_CONFIRMATION_SECRET (optional, used in the GitHub npx example), ALLOW_WRITES (optional; required only if you want mutation operations enabled), REQUEST_TIMEOUT_MS (optional), MAX_RETRIES (optional), CATALOG_CACHE_PATH (optional), READ_CACHE_TTL_MS (optional), EXECUTE_MAX_BODY_BYTES (optional), EXECUTE_BODY_PREVIEW_CHARS (optional).