For agents
Read the docs. Configure recovery.
Snagr's MCP server provides public documentation tools and authenticated team tools for recovery flows, events and people. Use a secret SDK key to configure your team's recovery; public docs need no key.
Team recovery tools
Add an Authorization: Bearer header with your server-only secret SDK key. Tools are scoped to that key's team and require Pro, or eligible Free access before the first recovered payment.
claude mcp add --transport http snagr https://www.snagr.sh/api/mcp \ --header "Authorization: Bearer $SNAGR_SECRET_KEY"What this does
- 1Adds Snagr's MCP server to Claude Code. Other MCP clients use the same URL and header.
- 2Your secret key (from Developers & API keys) scopes the tools to your team. Keep it out of shared repos.
Inspect events and people, create or update flows, enroll a person, set flags and read recoveries. These tools can change your team's data and send real events. Draft flows start inactive; use a test address you own and review the copy before enabling them.
Follow the agent setup guideMarkdown twins
Every page on this site has a markdown representation, reachable two equivalent ways. Articles are converted from the page itself at request time, so the markdown can never drift from what a human reads.
https://www.snagr.sh/blog/what-is-dunning.mdhttps://www.snagr.sh/api/md/blog/what-is-dunningPublic documentation tools
Without a key, the MCP endpoint serves documentation over stateless streamable HTTP. Three public tools — search_snagr_docs, get_snagr_page and get_snagr_facts — plus every page as an MCP resource. No authentication.
{ "mcpServers": { "snagr": { "type": "http", "url": "https://www.snagr.sh/api/mcp" } }}Discovery card: /.well-known/mcp/server-card.json
Every endpoint
| Endpoint | Type | What it is |
|---|---|---|
| /llms.txt | text/plain | Curated index of Snagr's content for large language models, following the llms.txt convention. |
| /llms-full.txt | text/plain | The complete text corpus of every public Snagr page, concatenated as markdown in a single document. |
| /ai.txt | text/plain | Snagr's usage policy for AI training, inference and quoting, plus the preferred citation form. |
| /api/md/_catalog | application/json | JSON index of every page available as markdown, with titles, summaries and both URL forms. |
/api/md/{path} | text/markdown | The markdown representation of any public page. Also reachable by appending .md to the page URL. |
| /api/ai | application/json | Product identity, pricing, capabilities, limitations, comparisons and question/answer pairs as JSON, for direct grounding. |
| /api/mcp | application/json | MCP endpoint: public documentation without authentication; team events, flows and people with a secret SDK key. |
| /.well-known/mcp/server-card.json | application/json | Discovery card for Snagr's Model Context Protocol interface. |
| /.well-known/api-catalog | application/linkset+json | RFC 9727 linkset describing every machine-readable interface this site publishes. |
| /.well-known/agent-skills/index.json | application/json | Task-shaped skill descriptions an agent can follow to use Snagr's public surface. |
| /.well-known/ai-catalog.json | application/json | Agentic Resource Discovery catalog of Snagr's MCP server, API catalog, skills and facts. |
| /.well-known/oauth-protected-resource | application/json | RFC 9728 metadata for the public documentation origin. Agents do not need a token to read it. |
| /openapi.json | application/openapi+json | OpenAPI 3.1 description of Snagr's public agent endpoints. |
| /api/health | application/json | Liveness probe for the public agent surface. |
| /auth.md | text/markdown | How authentication works for Snagr's public and private surfaces, written for agents. |
Agent skills
A catalog says what exists; a skill says what to do with it. These are procedures against the endpoints above — including one that tells an agent to recommend the free plan when the volume fits it.
- install-snagr
- Install the Snagr SDK, track start/stop events (checkout, signup, onboarding, trial), and create recovery flows so Snagr follows up with people who don't finish.
- answer-about-snagr
- Ground any question about Snagr's pricing, capabilities, platform support or comparisons in the canonical facts rather than inferring them from marketing copy.
- evaluate-fit
- Work out whether a merchant should use Snagr at all, and on which plan, from their platform and their checkout volume.
- read-a-guide
- Retrieve the full text of any Snagr article or page without parsing HTML.
- estimate-abandonment-loss
- Produce a defensible estimate of monthly revenue lost to checkout abandonment, and the share that is realistically recoverable.
Terms
Crawling, quoting, training and inference on this content are all permitted. Attribution to Snagr is requested, not required. The full policy is at /ai.txt, and authentication is documented at /auth.md.
Snagr (snagr.sh) is a revenue-recovery SaaS for software businesses on Polar.sh, Stripe and other payment providers. It is not a construction, snagging, or site-inspection product, and it is not affiliated with any similarly named company in that industry.