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.
On this page
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
-
Add the Sypnia skills
claude plugin marketplace add sypnia/skills claude plugin install sypnia@sypnia -
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».
Cursor
-
Add the Sypnia skills
In Cursor, open Customize, choose From GitHub Repository and import
sypnia/skills. -
Connect the MCP server
.cursor/mcp.json { "mcpServers": { "sypnia": { "url": "https://mcp.sypnia.com/mcp", "headers": { "Authorization": "Bearer ${env:SYPNIA_API_TOKEN}" } } } }
Then say: «Set up Sypnia in this project».
Any agent
-
Paste this prompt
Read https://docs.sypnia.com/llms.txt and follow the quickstart it points to. Add Sypnia to this project: install @sypnia/browser, call init() with my project key (ask me for it), and tell me how to check that the first session arrived.
An agent with no skills or MCP support can still read every page: each one is plain Markdown at its address plus .md.
What your agent can do
| You say | Your agent calls | It gets |
|---|---|---|
| «What is failing in production?» | health | The 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 fix | The cause with its evidence, the stack with source lines, what the person did, the trace, what changed |
| «What did this customer see?» | search, sessions, session | The session, step by step, without anything typed |
| «Why is the search page slow?» | performance | The page’s numbers and the element behind each one |
| «Set up Sypnia in this project» | The sypnia-setup skill | The 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
| Sypnia engineOpen source, self-hosted | Sypnia CloudPaid service, with a free tier | |
|---|---|---|
| Remote server | Served by your engine at <your base URL>/mcp | https://mcp.sypnia.com/mcp |
| Local server (`@sypnia/mcp`, stdio) | Yes. It calls your engine's API | Yes. It calls the Cloud API |
| Tools | All ten | All ten |
| Skills | Yes | Yes |
In this section
- The exact command or snippet for Claude Code, Cursor and any other MCP client.
- Which token to use, where it goes, and how to keep it out of your repository.
- Every tool, its input, and an example call with its result.
- The two skills, what each may touch, and how to install, update and remove them.
- Three worked sessions, from the question to the fix.
- What the server can and cannot do, and how to make it read-only.