heroku-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Heroku MCP Server?

The Heroku MCP Server is a specialized implementation of the Model Context Protocol (MCP) designed to facilitate seamless interaction between large language models (LLMs) and the Heroku Platform, enabling LLMs to manage and operate Heroku resources.

How to use Heroku MCP Server?

To use the Heroku MCP Server, deploy it on Heroku and configure it with your Heroku API key. You can interact with it through various tools like Claude Desktop, Zed, Cursor, and others by adding specific configuration snippets.

Key features of Heroku MCP Server?

  • Direct interaction with Heroku resources through LLM-driven tools.
  • Secure access to Heroku APIs using the Heroku CLI.
  • Natural language interface for managing Heroku resources.

Use cases of Heroku MCP Server?

  1. Managing Heroku applications and resources through natural language commands.
  2. Automating deployment processes for applications on Heroku.
  3. Integrating LLMs with Heroku for enhanced application management.

FAQ from Heroku MCP Server?

  • What is the Heroku MCP Server used for?

It is used to facilitate interactions between LLMs and the Heroku Platform, allowing for efficient management of resources.

  • Is the Heroku MCP Server free to use?

Yes, the server can be deployed for free on Heroku, but usage may incur costs based on Heroku's pricing model.

  • How do I authenticate with the Heroku MCP Server?

You can authenticate by generating a Heroku authorization token using the Heroku CLI or through the Heroku Dashboard.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago