Heroku Code MCP

Takes a different approach to Heroku Platform API access by exposing just three tools: auth_status, search, and execute. Instead of generating dozens of endpoint-specific tools, you search operations in natural language, pick an operation_id, then execute it with path, query, and body params. Built for token efficiency and includes a dry run plus confirmation flow for mutations. The benchmarks show 94% lower token count in tool listings and 18x faster read operations compared to the official endpoint-per-tool MCP server. Works over HTTP by default, seeds auth from the Heroku CLI, and pairs with the separate heroku-skills repo when you want workflow guidance on top of raw API access.