Connect your agent
Give your coding agent Anvil's reviews, CI logs, workflows and setup tools through its MCP server. You sign in through the browser; there's no token to copy.
-
Add Anvil:
claude mcp add --transport http anvil https://itest.wicker.life/mcp -
In Claude Code, run
/mcp, chooseanviland Authenticate. -
Approve the access level in the browser window that opens.
-
Add Anvil and sign in:
codex mcp add anvil --url https://itest.wicker.life/mcp codex mcp login anvil -
Approve the access level in the browser window that opens.
-
Click Add to Cursor in Settings → Connect an agent, or put this in
.cursor/mcp.json:{ "mcpServers": { "anvil": { "url": "https://itest.wicker.life/mcp" } } } -
In Cursor's MCP settings, click Needs login next to
anvil. -
Approve the access level in the browser.
-
Click Install in VS Code in Settings → Connect an agent, or run:
code --add-mcp '{"name":"anvil","type":"http","url":"https://itest.wicker.life/mcp"}' -
Start the server from the MCP view and sign in when VS Code asks.
Any client with Streamable HTTP and OAuth needs only the address:
https://itest.wicker.life/mcp
A client that only speaks stdio can use a bridge:
npx mcp-remote https://itest.wicker.life/mcp
You're connected #
The agent is listed under Connected agents in Settings → Connect an agent, with its access level and when it was last used. Try:
What needs my attention in Anvil?
Pick an access level #
The browser asks what the agent may do. You can change it by disconnecting and connecting again.
| Level | The agent can |
|---|---|
| Read only | See repositories, CI runs and logs, tests, reviews, findings, learnings and spend |
| Read and write | Also run, re-run and cancel CI, request reviews, resolve findings, apply suggestions, comment and start agent tasks |
| Read, write and setup | Also create repositories and mirrors, turn reviews on or off, change .anvil.yaml and add SSH keys |
Without a browser: API tokens #
For CI jobs, scripts and clients without OAuth, use a personal API token.
-
In Settings → Connect an agent, create a token under API tokens with the level it needs.
-
Store it in a secret store or an environment variable. It starts with
rvw_and is shown once. -
Send it as a header:
claude mcp add --transport http anvil https://itest.wicker.life/mcp \ --header "Authorization: Bearer $ANVIL_TOKEN"
The same token is the password for git over HTTPS on hosted repositories. A read-only token can clone but not push.
Next #
- MCP server Every tool, prompt and resource, with the level it needs.
- Find failing, slow and flaky CI What the agent reads when it asks why CI failed.