Back to Browse

Heystack Plugins MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://mcp.heystack.dev/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "dev-heystack-heystack": {
      "url": "https://mcp.heystack.dev/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

Reviews

No reviews yet

Be the first to review this server!