Track errors in your apps with a lightweight SDK. European-hosted, privacy-first, and simply priced.
Get started for free
A dashboard for you. An MCP server and an API for your coding agent.
Repeat errors group together, so 4,000 events read as one problem.
Source maps turn minified stack traces back into your original source.
Source maps guideResolved errors reopen on their own if they happen again.
Connect GitHub and get an explanation and a diff for any error. On Pro.
Start for free. Upgrade only when your project grows.
Two plans. No confusion.
We're independent and investor-free. Our only backers are our Pro customers, who fund every fix and feature we ship.
ObserverKit is an error tracking tool for JavaScript, TypeScript and React Native apps, built for AI coding agents. It captures errors in production, groups them, symbolicates stack traces with your source maps and alerts you. Your errors are also exposed over an MCP server and a REST API, so agents like Claude Code can triage and fix them. ObserverKit is hosted in Europe.
Yes. ObserverKit has a free plan with no credit card required: 500 errors per month, unlimited projects, 30-day retention, Telegram notifications, the MCP server and the REST API. The Pro plan costs €10 per month or €100 per year and adds 25,000 errors per month, 90-day retention, Slack and email notifications, email support and 20 AI fix proposals per month.
Yes, if you want a simpler error tracker. ObserverKit differs from Sentry in three ways: simple, transparent pricing instead of enterprise contracts; hosting in Europe, GDPR compliant by default; and a design built for AI agents. The MCP server and REST API are first-class, so your coding agent can read, triage and resolve errors without a human in the loop.
Add the ObserverKit MCP server to Claude Code with one command. Create an API key in your project settings, then run: claude mcp add --transport http observerkit https://api.observerkit.com/mcp --header "Authorization: Bearer YOUR_API_KEY". Claude Code can then read and triage your production errors. Any MCP client that supports streamable HTTP connects the same way, and the ObserverKit docs have a full walkthrough.
The ObserverKit MCP server provides five tools, all scoped to the project that owns your API key: list_error_groups to list errors with status, time and service filters; get_error_group for a symbolicated stack trace with source context; list_error_events for individual occurrences; resolve_error_group to close an error; and ignore_error_group to mute noise.
Yes, with your own coding agent. ObserverKit exposes your errors over MCP, so an agent like Claude Code can pull the day's new errors, fix them on a branch, run your tests, and open the pull request in your repository. The fixing and the pull request happen in your agent and your repo, not in ObserverKit. If you would rather not wire that up, the dashboard's AI fix proposal reads your linked GitHub repo and hands you an explanation and a diff to copy.
Yes. ObserverKit is hosted in Europe and GDPR compliant by default. Error events are stored on European servers and kept only for your plan's retention window: 30 days on Free, 90 days on Pro.
ObserverKit works with any JavaScript or TypeScript app. @observerkit/js is framework-agnostic and starts with one ObserverKit.init call, and the docs have step-by-step guides for React, React Router and Next.js. React Native and Expo apps use @observerkit/react-native. Source maps upload at build time through the Vite, Next.js and Metro plugins.