Give your assistant Ironfang
One remote MCP endpoint, a normal sign-in, no keys to paste. Ironfang Render, Ironfang Audit, Ironfang Finance and Ironfang Rig as tools in Claude Code and other MCP clients, acting for your organisation, with their work counted as ordinary usage inside the limits you set.
Connect Claude Code
Run /mcp, pick ironfang, choose Authenticate. Sign in at id.ironfang.com, pick the organisation the assistant should act for, allow the scopes. That is the whole setup.
claude mcp add --transport http ironfang https://mcp.ironfang.com/mcpClaude Desktop and claude.ai
Settings → Connectors → Add custom connector. Name it Ironfang, enter the endpoint below, and complete the same sign-in.
https://mcp.ironfang.com/mcpWhat the server covers
One endpoint, one sign-in, and the tools of each product the organisation uses. The assistant sees a tool only as far as the scopes you allow.
| Product | MCP support | Through an assistant |
|---|---|---|
| Ironfang Render | Available (18 tools) | Screenshots, PDFs, capture bundles, QR codes, template renders, clips, batches, signed render URLs, webhook delivery destinations, jobs and usage. Storage destinations carry credentials and stay in the portal. |
| Ironfang Audit | Available (9 tools) | Read sites, audits, findings, rules and usage, and start a bounded audit of a site. Changing a rule, a site, a monitor or a finding stays in the portal and the REST API. |
| Ironfang Finance | Reference tools only (3 tools) | Reference only: what a validation rule means and how to fix it, and which rulesets the validator runs. Validating and generating documents, results and jobs are REST-only; the Ironfang Finance API takes a platform API key and has no OAuth delegation yet. |
| Ironfang Rig | Available (19 tools) | Projects and suites, runs and their resources, the timeline and waits, replay, deterministic faults, the local connector bootstrap, evidence manifests and signed receipts. |
| Ironfang Analytics | Not available | Not yet available over MCP. Sites, recordings, playback and deletion are in the portal and the REST API. |
| Ironfang Security | Not available | Not yet available over MCP. Domains, verification, scans, findings and rechecks are in the portal; during the preview the Security API takes a signed-in user's token and refuses delegated MCP tokens and API keys. |
Ordinary usage, your limits
No MCP fee. Work an assistant does through a connection is ordinary usage of each product, as it is through the API: it draws on the account's free allowances and, with pay as you go switched on, stays inside the monthly usage limit and any product limit you set. Paid work that would pass a limit is refused before it starts, so an agent in a loop cannot spend past it. Reads and Ironfang Finance rule lookups are free.
Nothing to leak
The assistant never holds an API key. It gets a short-lived token addressed only to the MCP endpoint, and every product call uses a two-minute delegated token limited to the scopes you allowed. Disconnect from the portal at any time.
Durable work, small context
Every render is a durable job with an envelope, not bytes in the conversation. Results are hosted for 24 hours and fetched through 15-minute signed links.
For developers and agents
The endpoint is https://mcp.ironfang.com/mcp: streamable HTTP, OAuth 2.1 with PKCE against id.ironfang.com, listed in the MCP Registry as com.ironfang/ironfang. A client discovers the rest from the endpoint's 401 challenge. Every tool, its input schema, scopes and whether it reads, writes or spends is published without a token at /.well-known/ironfang-mcp.json, generated from the server's own definitions. Claude Code and claude.ai are tested; other clients connect through the same standards. Tool names are a compatibility contract: we add, we do not silently change.