Can Replit read my production errors?

Yes, once Runheed is connected. Replit calls the MCP tools to list recent errors, search them, and read one in full with its stack trace, breadcrumbs, request and release, then answers in the chat.

Do I need an API key to connect Replit?

No. Replit connects to the remote server URL and you sign in to Runheed once (OAuth). An agent key is only needed if you use the local server instead.

What can Replit change in Runheed?

Only an error's status: resolve (with a note such as the commit hash), ignore or unignore, and each can be flipped back. It cannot change projects, billing or keys, and Runheed has no access to your code or servers.

Do I need a plan to connect?

Yes, connecting needs an active plan. Plans start at $29/month for 50,000 events a month.

How to connect Runheed to Replit

Replit Agent connects to MCP servers by URL, so one button adds Runheed and one prompt adds error reporting to your Node.js or Python app.

Add to Replit Opens Replit with the Runheed server filled in; sign in when it asks. No key to copy.

Runheed is an error tracker with an MCP server: your app reports exceptions through a small SDK, and Replit reads them through the server below.

Steps

Click Add to Replit above (or + Add MCP server, then enter the display name and URL and click Test & save).
Replit walks you through sign-in. The first time it connects, a runheed.com sign-in page opens. Sign in with your email link, check the workspace and click Allow. The app then shows up in Settings > Agent keys under Connected apps, where Disconnect removes it.
Create a project in Runheed and add its DSN to your Repl as the secret RUNHEED_DSN. Then paste the prompt below into Replit Agent.

Where the config lives: replit.com/integrations, under MCP Servers. Use the button above, or + Add MCP server with the URL below.

Server URLtext

https://runheed.com/api/mcp

Prompt for Replit Agenttext

Add Runheed error tracking to this app, and use the Runheed MCP server (https://runheed.com/api/mcp) to check it worked.
Node.js: install https://runheed.com/dl/runheed-0.1.0.tgz, then at server start: import runheed from 'runheed'; runheed.init({ dsn: process.env.RUNHEED_DSN, environment: 'production' }). If this is Express, add app.use(expressErrorHandler()) from 'runheed' after all routes. In catch blocks that swallow errors, call runheed.captureException(err) and then await runheed.flush().
Python: install https://runheed.com/dl/runheed-0.1.0-py3-none-any.whl, then at startup: import os, runheed; runheed.init(dsn=os.environ["RUNHEED_DSN"], environment="production"). In except blocks that swallow errors, call runheed.capture_exception(e).
Do not hardcode the DSN. Then add a temporary route that raises an error, call it once, confirm it with runheed_get_recent, and remove the route.

The npm and PyPI releases are not out yet, so these commands install the same package files straight from runheed.com. Nothing else changes when the registry versions ship.

Errors in the browser part of the app are not captured; there is no browser SDK yet.

Check that it works

In Replit Agent: "What are the newest unresolved Runheed errors?"

If the agent reports a problem

Every Runheed tool error says what went wrong and where to fix it. The common ones:

"Start a plan to connect" on the sign-in page: Connecting needs an active plan. Pick one on that page, pay in Stripe Checkout, then connect again from the app.
The app keeps asking you to sign in: The app was disconnected in Settings (its key was revoked). Sign in again and click Allow.
"RUNHEED_API_KEY is not set": The key is missing from the server env. Add it and restart the client.
"That is a project key (pk_...)": You pasted the DSN key. The MCP server needs an agent key that starts with al_.
"This agent key is not recognised": Typo, or the key was revoked. Create a new one in Settings; keys are shown once.
"The workspace has no active plan": Choose a plan or fix the card in Settings > Billing. The key works again as soon as the plan is active.
"No errors have been reported yet": The agent side works. Check that the app has RUNHEED_DSN set and calls runheed.init() at startup.

Questions

Can Replit read my production errors?: Yes, once Runheed is connected. Replit calls the MCP tools to list recent errors, search them, and read one in full with its stack trace, breadcrumbs, request and release, then answers in the chat.
Do I need an API key to connect Replit?: No. Replit connects to the remote server URL and you sign in to Runheed once (OAuth). An agent key is only needed if you use the local server instead.
What can Replit change in Runheed?: Only an error's status: resolve (with a note such as the commit hash), ignore or unignore, and each can be flipped back. It cannot change projects, billing or keys, and Runheed has no access to your code or servers.
Do I need a plan to connect?: Yes, connecting needs an active plan. Plans start at $29/month for 50,000 events a month.

Next: the find, fix and resolve loop, and what Replit can see.

Still need the SDK side? See the setup docs or setup by framework, or tell Replit: Read https://runheed.com/SETUP.txt and set up error tracking. Official reference: Replit MCP docs.

Plans from $29/mo See what Replit readsCancel any time from the billing portal

Other clients: claude.ai · ChatGPT · Claude Code · Cursor · Claude Desktop · VS Code · Windsurf · Codex CLI · Gemini CLI · Lovable · Bolt · Antigravity · Zed · Cline