Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Heystack

by heystack-hqversion 0.1.0i★ –iRuns in the cloud
Registry namedev.heystack/heystack

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Search & AI memory
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http heystack https://mcp.heystack.dev/mcp --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "heystack": {
      "url": "https://mcp.heystack.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "heystack": {
      "type": "http",
      "url": "https://mcp.heystack.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret HTTP header
    Bearer (optional — OAuth via Clerk is used when omitted)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain heystack.dev (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7249 servers in this category
  • Published to the registry more recently than 43% of the other 7249 servers in this category
  • Basic checks equal to or better than 100% of the other 7249 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Heystack safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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=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.json URL to ?toolsets=core,manage,team (or advanced). 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-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.

`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 heystack plugin'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.

Ask PopNx