Docs

Sypnia documentation

Sypnia watches your app in production and tells you in plain words what broke, for whom and since when. Then it hands the fix to your coding agent: as a ready prompt, through an MCP server, or as a pull request.

Install the SDK

One line, then three. Works in any web app.

npm

npm install @sypnia/browser
import { init } from '@sypnia/browser';

init({ project: 'YOUR_PROJECT_KEY' });

Full quickstart

Let your coding agent do it

Add the Sypnia skills and connect the MCP server. Then ask your agent to set up Sypnia.

Claude Code

  1. Add the Sypnia skills

    claude plugin marketplace add sypnia/skills
    claude plugin install sypnia@sypnia
  2. Connect the MCP server

    claude mcp add --transport http sypnia \
      https://mcp.sypnia.com/mcp \
      --header "Authorization: Bearer YOUR_API_TOKEN"

Then say: «Set up Sypnia in this project».

What the skills do

Paid service, with a free tier

Use Sypnia Cloud

  • You read it inThe full app: replay player, performance, uptime, daily summary, teams.
  • AIIncluded. Pull requests opened by the Sypnia GitHub App.
  • AlertsE-mail and in the app, plus a daily summary.
  • CostFree tier, then from USD 10 a month.

Open source, self-hosted

Run the open-source engine yourself

  • You read it inThe API, the MCP server, the CLI and the Console, one built-in page.
  • AIYour own model key. Off until you set one.
  • AlertsRecorded, plus a webhook. No e-mail sender by default.
  • CostFree. You pay for your own infrastructure.

Sypnia Cloud is not a different product. It is our deployment of the same engine, plus accounts, billing, the full app and the GitHub App. Compare the two, line by line

The map

Every page says whether it is about the engine, Sypnia Cloud or both, and whether the thing exists at launch.

Written for people and for coding agents. Every page is also plain Markdown: add .md to its address, or use the «Copy page for your agent» button. Agents can start from the index.

llms.txtllms-full.txt

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close