Forge can let software and AI tools that your company chooses read your company's Forge data. There are two ways in, and both read the same data:
- The MCP server, for AI tools. Any AI tool that supports MCP can connect and ask Forge questions, such as "what walks did I do today?". Its address is
https://api.forge.equipment/mcp. - The public API, for software. A program your company runs, or a product that serves many Forge customers, reads the same data with plain web requests, starting at
https://api.forge.equipment/v1.
An owner or admin may separately allow an app to create jobs and their clients, edit job details, link external job IDs, decide and sync daily sweep segments, merge duplicate jobs, record estimate outcomes, record the prices sent to clients and what work actually cost, and propose rate changes for an owner or admin to approve. These edits are recorded. Connected apps cannot change money, permissions or ownership, or delete records. API keys remain read only.
Approve each connection
Data access is available by default. An owner or admin can turn it off in Settings. Each connection still needs its own approval.
- An AI tool or app opens a Forge page where an owner or admin signs in, picks one company, reads what the tool can read and chooses Allow read access. When Forge offers edits, the page also has a box, off to start with, that lets the tool make changes; with it ticked the button reads Allow read and edit access. See reads and edits.
- Or an owner or admin creates an API key on the web. Creating the key is the approval.
Owners and admins can connect apps and create API keys. A project manager or estimator can connect an AI tool to the MCP server for themselves, to read only what Forge shows them in the app; they cannot create API keys or use the public API. Every owner and admin can see every connection and key for their company, and end any of them.
One company, all of it
Each connection reads one company, the one picked when it was approved. No request names a company: the company comes from the connection or the key itself, so a connection can never read another company, even when the person who made it belongs to more than one.
A connection reads that whole company. You cannot pick a set of jobs: consent is all or nothing for each company.
Where to go next
- Connect an AI tool, with its own sign-in or with an API key.
- See what is shared and what never leaves.
- Read about reads and edits: what a tool may change if you let it, and what it never can.
- Ask your AI tool about walks and transcripts.
- End access for one tool, one key, or everything at once.
- Developers: the API reference, registering an app that serves many Forge customers, and how verification works.
- What changed, in the changelog.
Getting help
If a connection, an API key or anything in this manual does not work the way it says, email team@forge.equipment. We aim to reply within one business day, and that covers connected apps, AI tools and API keys too. It is the same inbox and the same promise as on our Support page.