The Heroku Platform MCP Server enables large language models to interact directly with Heroku resources through a Model Context Protocol (MCP) implementation, allowing LLMs to read, manage, and operate Heroku Platform resources with natural language interfaces.
Generate a Heroku authorization token using one of these methods:
heroku authorizations:create
Or retrieve an existing token:
heroku auth:token
You can also create a token through the Heroku Dashboard by:
Add this snippet to your claude_desktop_config.json
:
{
"mcpServers": {
"heroku": {
"command": {
"path": "npx",
"args": ["-y", "@heroku/mcp-server"]
},
"env": {
"HEROKU_API_KEY": "<YOUR_HEROKU_AUTH_TOKEN>"
}
}
}
}
Add this snippet to your Zed settings.json
:
{
"context_servers": {
"heroku": {
"command": {
"path": "npx",
"args": ["-y", "@heroku/mcp-server"]
},
"env": {
"HEROKU_API_KEY": "<YOUR_HEROKU_AUTH_TOKEN>"
}
}
}
}
Add this snippet to your Cursor mcp.json
:
{
"mcpServers": {
"heroku": {
"command": {
"path": "npx",
"args": ["-y", "@heroku/mcp-server"]
},
"env": {
"HEROKU_API_KEY": "<YOUR_HEROKU_AUTH_TOKEN>"
}
}
}
}
Add this snippet to your Windsurf mcp_config.json
:
{
"mcpServers": {
"heroku": {
"command": {
"path": "npx",
"args": ["-y", "@heroku/mcp-server"]
},
"env": {
"HEROKU_API_KEY": "<YOUR_HEROKU_AUTH_TOKEN>"
}
}
}
}
Add this snippet to your Cline config.json
:
{
"mcpServers": {
"heroku": {
"command": {
"path": "npx",
"args": ["-y", "@heroku/mcp-server"]
},
"env": {
"HEROKU_API_KEY": "<YOUR_HEROKU_AUTH_TOKEN>"
}
}
}
}
Add this snippet to your VSCode settings.json
or .vscode/mcp.json
:
{
"mcp": {
"servers": {
"heroku": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@heroku/mcp-server"],
"env": {
"HEROKU_API_KEY": "<YOUR_HEROKU_AUTH_TOKEN>"
}
}
}
}
}
Add this snippet to your Trae mcp_settings.json
:
{
"mcpServers": {
"heroku": {
"command": {
"path": "npx",
"args": ["-y", "@heroku/mcp-server"]
},
"env": {
"HEROKU_API_KEY": "<YOUR_HEROKU_AUTH_TOKEN>"
}
}
}
}
You can debug the server using the MCP inspector:
npx @modelcontextprotocol/inspector heroku-mcp-server
Or when developing locally:
cd /path/to/servers
npx @modelcontextprotocol/inspector dist/index.js
For VS Code debugging with breakpoints:
Store your Heroku auth token in VS Code settings:
{
"heroku.mcp.authToken": "your-token-here"
}
Use the Run and Debug launcher with the "MCP Server Launcher" configuration.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.