Heroku MCP server

<!-- When creating a PR, be sure to prepend the PR title with the Conventional Commit type (`feat`, `fix`, or `chore`). This is how we manage package versioning and generating CHANGELOG notes. Examples: - "feat: add growl notification to spaces:wait" - "fix: handle special characters in app names" - "chore: add dist directory to .gitignore" The expected Conventional Commit types are listed below. Learn more about [Conventional Commits](https://www.conventionalcommits.org/). --> ## Summary <!-- Brief description of the changes in this PR. --> ## Type of Change ### Breaking Changes (major semver update) - [ ] Add a `!` after your change type to denote a change that breaks current behavior ### Feature Additions (minor semver update) - [ ] **feat**: Introduces a new feature to the codebase ### Patch Updates (patch semver update) - [ ] **fix**: Bug fix - [ ] **perf**: Performance improvement - [ ] **deps**: Dependency upgrade - [ ] **revert**: Revert a previous commit - [ ] **docs**: Documentation change - [ ] **style**: Styling update - [ ] **chore**: Change that does not affect production code - [ ] **refactor**: Refactoring existing code without changing behavior - [ ] **tests**: Add/update/remove tests - [ ] **build**: Change to the build system - [ ] **ci**: Continuous integration workflow update ## Testing **Notes**: <!-- Add any context/setup necessary for testing. --> **Steps**: 1. Replace this text with a list of steps used to validate changes or type 'Passing CI suffices'. 2. ... ## Screenshots (if applicable) ## Related Issues GitHub issue: #[GitHub issue number] GUS work item: [WI number](WI link)