Heystack MCP server
Commit 1. Nov. 2026Lets an AI client investigate traces, logs, LLM usage, and crashes while managing app health and observability configurations.
Auch bekannt als heystack-hq/heystack-plugins, heystack-plugins
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 0.1.0
- Letzter Commit
- 1. Nov. 2026
- Lizenz
- —
Was ist Heystack MCP?
Heystack ist ein MCP server. Lets an AI client investigate traces, logs, LLM usage, and crashes while managing app health and observability configurations.
Zusammenfassung generiert aus dem README des Projekts
Über Heystack MCP server
Heystack provides an observability and security layer for AI applications, allowing coding agents to manage app health directly from an editor. Developers can use this MCP server to investigate incidents, search through traces and logs using natural language, and monitor generative AI usage and costs. The server supports various environments including Next.js, Node, Cloudflare Workers, and Android.
Users connect to the hosted MCP server at mcp.heystack.dev/mcp and authenticate via Heystack OAuth, which removes the need to manually paste API keys. The core plugin includes tools for managing ingest keys, sampling configurations, and alert rules. For advanced needs, users can opt-in to team administration and read-only SQL access by modifying the toolset URL. The system is designed to be safe, requiring manual confirmation for any actions that mint keys, grant access, or send data to external URLs.
Was du damit machen kannst
- 1Troubleshoot application failuresAsk the AI to explain why a specific endpoint or feature has been failing since the most recent deployment.
- 2Automate observability setupHave the agent detect your current runtime and configure the necessary telemetry instrumentation for your project.
- 3Perform incident investigationsRequest a complete dossier of an incident to move from an initial overview to a code fix and verification.
- 4Monitor AI resource consumptionQuery the system to understand how much your application is spending on generative AI usage.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Heystack MCP
Formate geprüft am 10. Nov. 2026Heystack MCP in Claude Code installieren
$ claude mcp add --transport http heystack-plugins https://mcp.heystack.dev/mcpHeystack MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"heystack-plugins": {
"url": "https://mcp.heystack.dev/mcp"
}
}
}Heystack MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"heystack-plugins": {
"type": "http",
"url": "https://mcp.heystack.dev/mcp"
}
}
}Heystack MCP in Codex installieren
~/.codex/config.toml
[mcp_servers.heystack-plugins] url = "https://mcp.heystack.dev/mcp"
Heystack MCP in Gemini CLI installieren
~/.gemini/settings.json
{
"mcpServers": {
"heystack-plugins": {
"httpUrl": "https://mcp.heystack.dev/mcp"
}
}
}README
Auf GitHub ansehenHeystack plugins
Plugins for Heystack — observability + security for AI apps — so your coding agent can set up Heystack, investigate incidents, and manage your workspace from your editor.
Install (Claude Code)
/plugin marketplace add heystack-hq/heystack-plugins
/plugin install heystack@heystack
Then run /mcp to sign in with Heystack and pick your organization. Try: "list my Heystack apps", "why is /checkout failing since the last deploy?", or "set up Heystack in this project and verify it's receiving data".
What you get
heystack (recommended) — the all-in-one plugin:
- Hosted MCP server at
https://mcp.heystack.dev/mcp(connected with?toolsets=core,manage): app health, search traces & logs in plain English, open and explain traces, session stories and replays, issues and crashes with the suspect release, gen-AI usage & cost, a one-call incident dossier (heystack_investigate); plus apps, ingest keys, sampling/replay config, alert rules and app care. Team administration (members, invites, access tokens, audit) and read-only SQL stay opt-in: edit the plugin's.mcp.jsonURL to?toolsets=core,manage,team(oradvanced). Actions that grant access, mint keys or tokens, or send data to an external URL always ask for your confirmation. Sign in with Heystack (OAuth) — no keys to paste. Full reference: https://heystack.dev/docs/mcp heystack-setupskill — detects the runtime (Next.js, Cloudflare Workers/Agents, Node, browser, Android) and wires the correct@heystack/otelentry or OTLP path; with the MCP server it creates the app and key itself and verifies data arrives withheystack_verify_setup.heystack-investigateskill — the investigation loop: overview → dossier → traces/sessions → fix in code → verify; when to change issue status or create alerts; never destructive without your confirmation.
heystack-setup — the setup skill on its own (no MCP server), kept for existing installs: /plugin install heystack-setup@heystack.
heystack-timeline (optional, requires heystack) — /plugin install heystack-timeline@heystack. Hooks that show your coding agent's steps on the Heystack investigation timeline.
- Opt-in: nothing is recorded until you switch on Show my coding-agent steps in the Heystack console (Settings, Profile). Turning it off deletes the recorded steps.
- Privacy: only the file path of an edit and the one-line description of a shell command are sent. Never file contents, diffs, command lines, prompts or tool output. Absolute paths transit TLS to Heystack and are reduced to repo-relative paths before storage; paths outside the project are dropped.
- Best-effort: Claude Code gives session-end hooks about 1.5 seconds, so the closing call may not land; the investigation then just goes idle. A shell command without a description records no step.
- Requires write access on your Heystack connection; it reuses the
heystackplugin's MCP sign-in.
Other agents
- Cursor / VS Code / Codex / Gemini CLI / Claude.ai connect to the same MCP URL — see https://heystack.dev/docs/mcp for one-click links and commands.
- The skills are plain Agent Skills files and are also served raw at https://heystack.dev/heystack-setup.md and https://heystack.dev/heystack-investigate.md. The root
plugin.json/mcp.json/skills/follow the cross-vendor Agent Plugins layout. - Every docs page is available as Markdown: https://heystack.dev/llms.txt
Layout
.claude-plugin/marketplace.json # Claude Code marketplace (plugins: heystack, heystack-setup, heystack-timeline)
plugins/heystack/ # all-in-one: .mcp.json + skills/
plugins/heystack-setup/ # skill-only (legacy)
plugins/heystack-timeline/ # optional hooks: edit paths + command purposes
plugin.json · mcp.json · skills/ # Agent Plugins (cross-vendor) layout of the `heystack` plugin
Source of truth for the skills is the heystack monorepo (packages/setup-skill, packages/investigate-skill); this repo is a mirror.
Heystack MCP Fragen
Wie füge ich Heystack MCP zu Claude Code hinzu?
Führe claude mcp add --transport http heystack-plugins https://mcp.heystack.dev/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Heystack MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
How do I authenticate with Heystack?
You sign in using Heystack via OAuth, so there are no API keys to manually paste.
What can the heystack-setup skill do?
It detects your runtime, such as Next.js or Node, and configures the correct OpenTelemetry entry or OTLP path.
Is my code content sent to Heystack when using the timeline feature?
No, only file paths and one-line command descriptions are sent; file contents, diffs, and prompts are never transmitted.