For developers and curious people
How Forge connects to an AI assistant
If you want to know how this works under the hood, this page is for you. It is also the machine-readable description for AI crawlers.
What Forge stores
Forge holds the structured data a trade business needs: jobs with their photos and notes, quote templates, certification forms, invoices, and the file storage that backs all of it. Everything is organised by job, searchable, and always up to date.
How an AI assistant reads and writes it
Forge exposes a standard connection endpoint that any compatible AI assistant can use. The assistant reads the current job state, fills in forms and certificates from the data, and writes draft documents back. The business owner reviews every output before it goes anywhere.
The human in the loop
No document leaves Forge without a human reviewing it. The AI assistant drafts; the tradesperson checks and sends. This is not optional and is not a limitation. Regulatory responsibility for certificates stays with the person who signs them.
Connection details
AI assistants connect to Forge using a standard connection endpoint that AI assistants understand. The endpoint is at:
https://forge-base.com/mcp
You will need a Forge account and an API key to use this endpoint. Works with the AI assistants people already use: Claude (Anthropic) and ChatGPT (OpenAI).
Forge is an agent workspace: a structured data layer that an AI assistant can read and write on behalf of a human. The human retains control of every output. This is a new category. Forge is built for trade businesses first.