The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Heystack listing page.
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.
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".
heystack (recommended) — the all-in-one plugin:
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/mcpheystack-setup skill — detects the runtime (Next.js, Cloudflare Workers/Agents, Node, browser, Android) and wires the correct @heystack/otel entry or OTLP path; with the MCP server it creates the app and key itself and verifies data arrives with heystack_verify_setup.heystack-investigate skill — 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.
plugin.json / mcp.json / skills/ follow the cross-vendor Agent Plugins layout.Source of truth for the skills is the heystack monorepo (packages/setup-skill, packages/investigate-skill); this repo is a mirror.