Set up Anchr.ing with your AI agent
The MCP server for coding assistants, llms.txt, and rule files for Claude Code, Cursor, Copilot and other agents, so the integration comes out right the first time.
- You get
- Your coding agent set up with the MCP server and rule files, so the integration comes out right the first time.
- For
- Backend developer, Frontend developer
- Time
- About 5 min
- Products
- Machines and AI
Anchr.ing is meant to be set up by your coding agent in one go. Give it the MCP server, the rule file for your agent and one prompt.
1. Connect the MCP server
claude mcp add anchring -- npx -y @anchring/mcpRules for the agent: add CLAUDE.md to CLAUDE.md
It carries the SDK reference and these guides for its SDK version, works offline, and its integration_plan tool writes the setup for your framework: install command, apps to register, environment variables and files. Other agents: see the MCP server's README.
Self-hosted or local install: set ANCHRING_DOMAIN to its base domain and every tool targets it: claude mcp add anchring -e ANCHRING_DOMAIN=auth.example.com -- npx -y @anchring/mcp (a local stack: its host:port, plus ANCHRING_SITE_ORIGIN for the origin its dashboard is served from).
2. Add the rules for your agent
The rules tell the agent which entry point fits each part of your app, that the SDK does PKCE and storage, where secrets go, and never to invent endpoints. Download the file for your agent into your project:
CLAUDE.md, or .claude/skills/anchring/SKILL.md.cursor/rules/anchring.mdc.github/copilot-instructions.mdAGENTS.mdcurl -s https://anchr.ing/ai/CLAUDE.md >> CLAUDE.md # Claude Code (appends)
mkdir -p .cursor/rules && curl -so .cursor/rules/anchring.mdc https://anchr.ing/ai/anchring.mdc # Cursor
mkdir -p .github && curl -s https://anchr.ing/ai/copilot-instructions.md >> .github/copilot-instructions.md
curl -s https://anchr.ing/ai/AGENTS.md >> AGENTS.md # Codex, Windsurf and others3. Ask
Register the apps first (Getting started), then:
Add Anchr.ing sign-in to this app with @anchring/auth: project acme, environment test.
The web app's client id is test_…, the API's identifier is acme-api.
Sign users in from the web app, protect the API, and keep secrets out of the code.The agent asks for anything it can't find. Check the result yourself: sign in on test, call the API with and without a token (200, then 401), and look for secrets in the diff.
Docs for any agent
llms.txt indexes the guides and rule files; llms-full.txt is the rules, every guide and the SDK reference in one Markdown file. Both are generated from the same docs as these pages.
Every option, error and token type: the SDK README.