Foreman · Assistant / MCP · Sheet A

Ask Foreman anything. Or plug in your own AI.

Use the built-in Foreman Assistant, or connect Claude, Cursor, ChatGPT or Copilot via MCP. Same 100+ grounded tools, same OAuth 2.1 security, same audit trail — no matter which path your team picks.

100+

Tools

Off by default

Per-project opt-in

OAuth 2.1

PKCE · revocable

100%

Auditable

Sound familiar · Today

Every PM, BIM lead, and DC has lived these.

Every project manager, BIM coordinator, and document controller has faced these problems.

!Pain · 01

QA setup is slow.

Drafting a naming regex, picking zone templates, wiring validation lists — translating a standard into rule configs eats a full afternoon. Your AI should be writing the rules for you.

!Pain · 02

Running checks is manual.

Pick folders, pick a ruleset, wait, review, export, repeat. Every time a file changes. There's no ergonomic way to say "recheck these three files and tell me what changed".

!Pain · 03

Context switching tax.

Jumping between Autodesk Forma, spreadsheets, email, and chat tools. Each switch breaks your flow and loses the thread.

!Pain · 04

Complex multi-step workflows.

Onboarding a team means: create project, deploy folders, add members, assign roles, configure access. 50+ clicks. Triaging 300 violations across 7 files is equally tedious.

!Pain · 05

No programmatic access.

Autodesk Forma's UI is the only interface. No CLI, no automation, no scripting — unless you build one yourself.

!Pain · 06

Documentation drift.

Your QA standard lives in a PDF somewhere. Translating it into actual enforceable rules — and keeping them in sync — is on you.

How it works · Procedure

Pick your path. Same tools either way.

Start in Foreman, or bring your own AI — no coding required, full audit on both.

01Step · 01

Open the Foreman Assistant

It's already inside the dashboard — nothing to install. Or connect Claude, Cursor, ChatGPT, or Copilot as an MCP client via OAuth 2.1 (60-second setup).

02Step · 02

Ask in plain English

"For @constructiq, list files modified in the last 30 days and give me a CSV." Pin projects with @, drop PDFs, get artifacts back. Every answer is grounded in real tool calls.

03Step · 03

Review, confirm, audit

Destructive actions wait for your confirmation. Every request and every tool invocation is logged and reviewable — see exactly what the AI did, when, and on whose behalf.

Ready to connect Claude to your own Forma account?

Start 14-day trial

14-day trial · Full access · No card on file

Features · Capabilities

Two ways in. One grounded toolset.

Foreman Assistant — built in

Open the dashboard and ask. Pin projects with @, drop PDFs, get CSVs back. Streaming answers, slash commands, artifact side panel. Zero setup.

Bring-your-own AI via MCP

Claude (Web/Desktop/Code), Cursor, ChatGPT, and Copilot connect via OAuth 2.1. Same 100+ tools, same permissions, same audit — dynamic client registration, no keys to paste.

End-to-end QA automation

Run checks, poll progress, export CSV, generate PDF reports, recheck specific files, acknowledge or waive violations in bulk — every step of the QA loop is a tool.

AI-drafted rule sets

"Draft a ruleset for Structural — files should be PROJ-ST-SHEET.pdf." The assistant calls the AI regex generator, creates the ruleset, and adds the rules. Authoring in chat, not a form.

100+ grounded tools

19 categories: QA & QC, files, custom attributes, members, roles, access requests, projects, scheduled jobs, and more. Every answer traces to a real tool call.

OAuth 2.1 + per-user scope

Authorization Code + PKCE. Opaque reference tokens. Instant revocation. Per-user permissions inherited from Autodesk — the AI only sees what you can already see.

Granular tool toggles

Admins disable individual tools tenant-wide or per user. Admin-only tools gated behind admin permissions. AI access is opt-in per project — off by default.

Full audit trail

Every request, every tool invocation — logged with user, timestamp, arguments, success/failure. Tenant-level kill switch to disable chat across the whole org in one click.

Attachments in, artifacts out

Drag-drop PDFs, Word, Excel, PowerPoint, CSV/TSV, images, plus 30+ text and code formats — the Assistant reads them all. It can also read any file stored in an APS project in place. Replies come back as downloadable CSVs, code snippets, or Mermaid diagrams in a side panel.

Proactive bug & feature capture

When you describe something broken or suggest an improvement, the Assistant offers to file it for you as a BugReport or FeatureRequest — always with a preview and your confirmation. Goes straight into the Foreman feedback board.

Pin folders, scope the AI

Pick one or more Autodesk Forma folders in the composer and they stay attached across turns. QA, search, stale-files, and storage analytics auto-narrow to the pinned scope — and dedicated tools summarise contents, custom-attribute coverage, and value breakdowns.

See it in action · Sheet T

Natural language meets real API calls.

Here's what a typical conversation looks like — same shape whether it's the Foreman Assistant or Claude-via-MCP below.

Claude + Foreman MCP Connected
Draft a ruleset for Structural — files should be PROJ-ST-SHEET.pdf and can't be older than 30 days

Drafting the regex, creating the ruleset, and adding two rules:

ai_generate_qa_naming_pattern(description: "PROJ-ST-SHEET.pdf")
create_qa_ruleset(name: "Structural standard")
add_qa_rule(type: NamingConvention, pattern: ^[A-Z]+-ST-…)
add_qa_rule(type: Freshness, maxAgeDays: 30)
Ruleset created with 2 rules. Ready to run. Want me to check the Structural folder now?
Yes, run it. Then acknowledge any freshness violations on files from the archive folder.

Kicking off the check and triaging on completion:

run_qa_check(folder: Structural, ruleSet: #new)
get_qa_check_progress×3   polling…
get_qa_check_results→ 47 files, 6 freshness violations
update_qa_violation_status(bulk, scope: archive, status: Acknowledged)
Pass rate 87%. 4 archive violations acknowledged, 2 active ones left. Export CSV or push to Forma Issues?
Connected tools ·QA & QCFilesMembersAccess RequestsProjectsReviewsScheduled Jobs

Off by default

Per-project opt-in

Tool toggles

Tenant · per user

Kill switch

One-click org-wide

Full audit

Every invocation

Governance · Controls

Built for the security review.

Five controls admins actually want — off by default, granular toggles, a single kill switch, full audit, and per-user scope.

01Control · 01

Off by default.

AI access is explicit opt-in. Enable only the projects you want the assistant to reach — new projects stay locked until an admin turns them on.

02Control · 02

Tool-level toggles.

Admins disable any of the 100+ tools tenant-wide or per user. Narrow the blast radius to just the surface area your org has approved.

03Control · 03

Tenant kill switch.

Disable AI chat completely across the organization with a single toggle. Useful during investigations, audits, or rollouts.

04Control · 04

Full audit trail.

Every request and tool invocation is logged with user, timestamp, arguments, and success/failure. Export, review, replay.

05Control · 05

Permissions honored.

Each session inherits the signed-in user's Autodesk permissions. No admin escalation, no cross-tenant leakage, no quiet privilege creep.

Where it runs · Clients

In Foreman. Or anywhere you already chat.

Same 100+ tools, same OAuth security, same audit — pick where your team works.

Built-in

Foreman Assistant

In the dashboard

Zero setup — open Foreman and ask. Floating widget on every page plus a full-page workspace with history, artifacts, and a resizable sidebar.

Claude

Web, Desktop & Code

Add Foreman as a custom MCP integration. OAuth flow handles auth automatically. All 100+ tools available in Claude Web, Desktop, and Code.

Cursor & ChatGPT

IDE & web

Add Foreman MCP in Cursor settings or ChatGPT's connectors. Browser opens for OAuth. Same tools in your IDE or the ChatGPT workspace.

Copilot

Windows & agents

Connect via MCP. Same OAuth 2.1 flow. Full tool access for Windows Copilot and compatible agents.

FAQ · Questions answered

Frequently asked questions.

Q · 01

What is the Foreman Assistant?

The Foreman Assistant is a built-in chat inside Foreman that already knows your hubs, projects, members, and files. Ask questions in plain English, upload PDFs, pin projects with @alias, and get downloadable CSVs back — every answer is grounded in real tool calls against your Forma data.

Q · 02

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI clients use external tools. Foreman exposes its 100+ tools through both the built-in Foreman Assistant and an OAuth 2.1 MCP server — so you can stay in Foreman or bring your own AI (Claude, Cursor, ChatGPT, Copilot) and get the same grounded capabilities.

Q · 03

Which AI clients are supported?

The Foreman Assistant runs in-app with no setup. External clients include Claude (Web, Desktop, Code), Cursor, ChatGPT, and Copilot — any MCP-compatible client connects via the same OAuth 2.1 flow.

Q · 04

How many tools are available?

100+ user-facing tools across 19 categories: QA & QC, projects, members, roles, files, access requests, transmittals, reviews, scheduled jobs, and more. The same toolset powers both the Foreman Assistant and external MCP clients. Admin-only tools are gated separately.

Q · 05

How does governance work?

AI access is off by default on every project — opt in per project. Admins can disable individual tools, tenant-wide or per user. There's a tenant-level kill switch to disable chat across the whole org. Every request and tool invocation is logged to a full audit trail, and the assistant only sees what the signed-in user can already see in Forma.

Q · 06

Is it secure?

Yes. Foreman's MCP server uses OAuth 2.1 with Authorization Code + PKCE. Tokens are opaque references (not JWTs), support instant revocation, and access is per-user scoped. No client secrets stored in MCP clients. Dynamic client registration follows RFC 7591.

Q · 07

Can I control which tools are available?

Yes. Admins enable or disable individual tools tenant-wide or per user. Admin-level tools are hidden from regular users by default. Every invocation is tracked with success/failure metrics for auditing.

Q · 08

Can I scope the AI to a specific folder?

Yes. Pin one or more Autodesk Forma folders to your chat session from the composer and they persist across turns. QA, file search, stale-files, and storage analytics automatically narrow to the pinned scope, and three dedicated tools — summarize_folder_contents, get_folder_attribute_schema, and get_folder_attribute_stats — answer "what's in this folder", "what metadata is populated", and "what are the value breakdowns" without any manual scoping.

Q · 09

Can I run specific rule sets on pinned folders?

Yes. Once a folder is pinned, ask something like "run the ISO 19650 Basic and Structural Naming rule sets on the pinned Drawings folder". The Assistant looks up the rule set IDs, calls run_qa_check with the pinned folder IDs plus the full list of rule sets (one check run can apply multiple rule sets at once), polls progress, and returns the results — recursive into subfolders by default.

Q · 10

Can I upload PDFs to the chat and run a QA check on them?

Yes. Drop PDFs into the composer and ask "run the ISO 19650 Basic rule set on these". The Assistant reuses the same QA engine as the UI's Local Upload path. QA history labels the run based on who triggered it: "Assistant" (links back to the conversation turn), "MCP" (external client like Claude Desktop or Cursor), "Scheduled", "Triggered" (webhook), or "Manual" (UI). PDFs are the only supported file type today — other uploaded formats are visible to the model but not QA-checked.

Q · 11

What can I do with natural language?

Run QA checks and export reports, draft rule sets from plain-English descriptions, acknowledge or waive violations, manage members, search files, assign roles, process access requests, view transmittals, track reviews, manage scheduled jobs — all by describing what you want.

Q · 12

Do I need to configure an external AI to use this?

No. The Foreman Assistant is built-in — open the dashboard and ask. If you prefer Claude, Cursor, ChatGPT, or Copilot, connect them via MCP and get the same 100+ tools. Both paths are included.

Q · 13

Is this included in the free trial?

Yes. Both the Foreman Assistant and MCP integration are fully available during the 14-day free trial on the Business plan. No credit card required.

Free resource · Assistant & MCP

Week-One Playbook

The checklist we give every new admin — from opting in one project to running the first AI-drafted rule set. Print it out, tick as you go.

No spam. Unsubscribe with one click.

14-day trial Full access No card on file See pricing

MCP · 001 / Your move

Connect Claude, Cursor, or ChatGPT in five minutes.

100+ Forma admin tools over secure MCP — same permissions, same audit trail, your choice of AI client.

14-day trial · Full access · No card on file

Not ready? № 01

Week-one playbook

Admin checklist for rolling out the Foreman Assistant without the panic.

No spam. Unsubscribe with one click.

You're offline — some actions may not work.

Connection lost

Attempting to reconnect to Foreman...

Connection lost

Retrying in --s Attempt - of -

Connection interrupted

Retrying in --s Attempt - of -