Heystack plugins
MCP serverMonitoring & opsObservability for AI apps: investigate traces, logs, LLM usage, replays and crashes; manage alerts.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use Heystack plugins
From the project's README
As published by heystack-hq/heystack-plugins in README.md.
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=all): 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, team and tokens. 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.
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)
plugins/heystack/ # all-in-one: .mcp.json + skills/
plugins/heystack-setup/ # skill-only (legacy)
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.
Advanced
- Delivery
- heystack MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
dev-heystack-heystack- Source
- github.com/heystack-hq/heystack-plugins
- Hosted endpoint
https://mcp.heystack.dev/mcp