Docs

MCP and skills

Connect 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.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. What your agent can do
  2. Where it runs
  3. In this section

Engine Cloud Sypnia hands the fix to the agent that wrote the code. This section is how: an MCP server your coding agent can ask, and skills that teach it to work with 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

What your agent can do

You sayYour agent callsIt gets
«What is failing in production?»healthThe open problems that hit the most people, checks that are down, pages that got slower
«Fix the pay button problem»problem, then resolve_problem after the fixThe cause with its evidence, the stack with source lines, what the person did, the trace, what changed
«What did this customer see?»search, sessions, sessionThe session, step by step, without anything typed
«Why is the search page slow?»performanceThe page’s numbers and the element behind each one
«Set up Sypnia in this project»The sypnia-setup skillThe SDK installed, the key from an environment variable, source maps in the build, a first check

The server reads. Its one write is marking a problem resolved, and you can switch that off. It never merges code and never returns replay recordings.

Where it runs

The Sypnia engine and Sypnia Cloud compared
Sypnia engineOpen source, self-hostedSypnia CloudPaid service, with a free tier
Remote serverServed by your engine at <your base URL>/mcphttps://mcp.sypnia.com/mcp
Local server (`@sypnia/mcp`, stdio)Yes. It calls your engine's APIYes. It calls the Cloud API
ToolsAll tenAll ten
SkillsYesYes

In this section

  • Connect

    The exact command or snippet for Claude Code, Cursor and any other MCP client.
  • Authentication

    Which token to use, where it goes, and how to keep it out of your repository.
  • Tools reference

    Every tool, its input, and an example call with its result.
  • Skills

    The two skills, what each may touch, and how to install, update and remove them.
  • Examples

    Three worked sessions, from the question to the fix.
  • Security

    What the server can and cannot do, and how to make it read-only.

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