Ironfang MCP · private beta

Give your assistant Renderwolf

One remote MCP endpoint, a normal sign-in, no keys to paste. Screenshots, PDFs, QR codes, clips and template renders from Claude Code and other MCP clients, spending your own credits inside a budget you set.

Connect Claude Code

claude mcp add --transport http ironfang https://mcp.ironfang.uk/mcp

Run /mcp, pick ironfang, choose Authenticate. Sign in at id.ironfang.uk, pick the organisation the assistant should act for, allow the scopes. That is the whole setup.

Tested 27 Aug 2026 with Claude Code.

Claude Desktop and claude.ai

Settings → Connectors → Add custom connector. Name it Ironfang, enter https://mcp.ironfang.uk/mcp, and complete the same sign-in.

Expected to work; not yet tested by us. Tell us when it does.

Your credits, your budget

No MCP fee. Renders spend ordinary Renderwolf credits; each connection also gets its own budget (a tenth of the plan's monthly credits by default) so an agent in a loop cannot empty the month.

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.

What "private beta" means here

The endpoint, authentication and Renderwolf tools are live and exercised with a real client. We have not yet published to the MCP Registry, Auditwolf tools follow the Auditwolf commercial release, and the tested-client table is short. Tool names are a compatibility contract: we add, we do not silently change.

Read the MCP reference