Auterim, inside
your coding agent.
A local, read-only MCP server. Before your agent edits code, it can check which provider changes reach it, what the deadlines are and which fixes are already prepared.A local, read-only MCP server. Your agent checks provider changes, deadlines and prepared fixes before it edits code.
- Read-only
- Runs on your machine
- 9 tools
Upgrade the Supabase client in checkout.
auterim_changes{ status: "needs_action", provider: "supabase" }1 change · Breaking · act by Feb 1 · 3 call sites in your codeauterim_change{ id: "chg_supabase_auth" }auth.signIn() removed · use signInWithPassword() · src/lib/auth.ts:42, :88, :131Supabase removes auth.signIn() on Feb 1. I’ll update the three call sites as part of the upgrade.
Two commands, then ask.
The server ships with the Auterim CLI and runs over stdio, the way Claude Code, Cursor and VS Code start local tools.
Sign in the CLI
Approve read-only access to one Product in your browser. In CI, set
Read-only · one Product · 30 daysAUTERIM_TOKENinstead.terminal$ npx auterim loginOpening your browser to approve…✓ Signed in · Northwind web · read-onlyAdd it to your agent
One line for Claude Code, a small config file for Cursor or VS Code.
stdio · Node.js 22.6+terminal$ claude mcp add auterim \ -- npx -y auterim@latest mcpWindowsRun it through
cmd /c npx -y auterim@latest mcpAsk about your stack
Your agent calls
Starts with auterim_overviewauterim_overviewfirst, then goes as deep as the question needs.coding agent · exampleAnything I should know before upgrading Supabase?toolauterim_changes{ provider: "supabase" }Breaking · auth.signIn() removed Feb 1 · 3 call sites in src/lib/auth.ts
Nine tools. All read-only.
The same evidence you see in Auterim, in a shape an agent can use before it touches your code. Pick one to see what it returns.
auterim_changesread-onlyExampleAssessed provider changes and whether they affect the Product. Filter to open work.
Requestauterim_changes({ "status": "needs_action", "provider": "supabase" })
Response[ { "id": "chg_supabase_auth", "provider": "supabase", "title": "auth.signIn() is removed", "action_required": true, "act_by": "2027-02-01" } ]
auterim_changesread-onlyExampleAssessed provider changes and whether they affect the Product. Filter to open work.
auterim_changes({ "status": "needs_action", "provider": "supabase" })
[
{
"id": "chg_supabase_auth",
"provider": "supabase",
"title": "auth.signIn() is removed",
"action_required": true,
"act_by": "2027-02-01"
}
]Your agent reads. Your team decides.
Every tool only reads. Anything that changes a decision happens in Auterim, where your team reviews it.
- Provider changes and why they matter to your code
auterim_changes · auterim_change - Dates to act by, soonest first
auterim_deadlines - Prepared fixes, Draft PRs and their CI state
auterim_fixes · auterim_optimization - Dependency health and open work
auterim_health · auterim_actions
- Resolve or dismiss a changeRecorded with who decided
- Request PreflightChecks a change against your code
- Request a fix or Draft PROpened for your review, never merged
- Local onlyRuns through the CLI on your machine over stdio. Web clients such as claude.ai and ChatGPT aren’t supported yet.
- One Product per sign-inAccess is read-only, expires after 30 days and can be revoked by owners and admins in Settings → Integrations.
- Included in every planThe CLI and its MCP server come with every Auterim plan. They need Node.js 22.6 or newer.
Give your agent the context.
The MCP server reads what Auterim already knows about your Product. Start by protecting one.