How do I give Cursor access to production errors?

Connect it

1. Install the Runheed SDK in the app that throws the errors and initialize it at startup (setup by framework).
2. Create .cursor/mcp.json with the block below. Use ~/.cursor/mcp.json instead to have it in every project.
3. Open Customize in the Cursor sidebar, find runheed and click Connect. Sign in and click Allow.
4. In the agent chat, ask "List unresolved Runheed errors from the last 24 hours."

{
  "mcpServers": {
    "runheed": {
      "url": "https://runheed.com/api/mcp"
    }
  }
}

The file holds only a URL, so it is safe to commit. The Cursor setup page has a one-click install and the local server with an agent key.

Make it check errors first

Connecting the server does not make the agent use it. A project rule does. Rules live in .cursor/rules and must use the .mdc extension; Cursor skips plain .md files in that folder. With a description and alwaysApply set to false, the agent includes the rule when it judges the description relevant. Set alwaysApply to true to include it in every chat.

---
description: Use when debugging a bug report, a failing request or anything broken in production
alwaysApply: false
---

Production errors from this app are in Runheed, available through the runheed MCP tools.

- Before debugging, call runheed_search_errors or runheed_get_recent and read the
  stack trace with runheed_get_error. Don't guess from the code alone.
- Write a failing test that reproduces the error before changing any code.
- After the fix is committed, call runheed_resolve_error with the commit hash.
- Never ignore an error unless I ask you to.

Cursor also reads a plain AGENTS.md in the project root, without the metadata. If your repository already has one, the same instructions can go there.

Decide what runs without asking

Cursor asks for approval before it uses an MCP tool by default. In Auto-review mode, allowlisted tools run immediately, and others go through its classifier. Reasonable split:

Prompts to try

• "What broke in production since the last deploy? Fix the top one and resolve it with the commit hash."
• "Show me the stack trace and breadcrumbs for the newest TypeError."
• "Did errors go up after yesterday's release?"
• "Write a failing test for the top error before you change any code."

Cursor Cloud Agents

Cursor's docs say Cloud Agents support MCP servers over HTTP and stdio, with OAuth, and that team servers set under Dashboard > Plugins & MCPs are available to them. They work on a separate branch and push changes for handoff. That fits a fix that arrives as a pull request. We have not run this path, so check the sign-in on your first run.