What changed in Forge's MCP server, its public API and this manual, newest first. Changes to the public API follow the rules in versioning.
October 2026
- Edit tools are on the MCP server. A tool an owner or admin has allowed to make changes can link a job to another system's id, update a job's contact, address, stage or archive flag, update a daily sweep segment, merge duplicate jobs, record an estimate's outcome, record the prices sent to a client and what work actually cost, and propose a rate change. These are the tools marked as changes in the tool list.
- Edits start off. The consent page has a separate box to allow them, and an owner or admin must tick it. Every change tool can be asked for a dry run first, and every change is recorded in your company's audit log.
- An API key still only reads. It can never use a change tool.
- A proposed rate change waits for an owner or admin to approve it in Forge's web app; nothing in your rate book moves until then.
- New page: reads and edits. The pages that called every connection read only now say what is true.
September 2026
- First edition of this manual: connecting an AI tool, API keys on both the MCP server and the public API, what is shared and what never leaves, walks and transcripts, revoking access, registering an app, and how verification works.
- The MCP server's tools and the public API's routes are as listed on Connect an AI tool and in the API reference.