Heystack

Official registry Cloud and DevOps

Observability for AI apps: investigate traces, logs, LLM usage, replays and crashes; manage alerts.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http heystack 'https://mcp.heystack.dev/mcp' --header 'Authorization: <Bearer <Heystack personal access token> (optional — OAuth via Clerk is used when omitted)>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "heystack": {
            "type": "http",
            "url": "https://mcp.heystack.dev/mcp",
            "headers": {
                "Authorization": "<Bearer <Heystack personal access token> (optional — OAuth via Clerk is used when omitted)>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Heystack plugins
  2. Install (Claude Code)
  3. What you get
  4. Other agents
  5. Layout

Heystack 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=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-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.

Other agents

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.

Frequently asked questions

What is Heystack?

Observability for AI apps: investigate traces, logs, LLM usage, replays and crashes; manage alerts.

How do I install Heystack?

It runs as a remote server. In Claude Code: claude mcp add --transport http heystack 'https://mcp.heystack.dev/mcp' --header 'Authorization: <Bearer <Heystack personal access token> (optional — OAuth via Clerk is used when omitted)>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Heystack need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Heystack open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Heystack?

It is published by heystack-hq. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.