Run Forge from your own AI client.

Ask Claude, ChatGPT or any MCP client to find weak pages, draft specs and FAQs, and prepare a publish. Same permissions, same audit trail, and nothing goes live without an explicit call.

Book a demo Connection guide

Your AI client · Forge MCPSample data

you Which HX products are missing lead time? Draft fixes, don't publish.

→ forge_aeo_families_list { storefront: "production" }
→ forge_geo_pages_list { category: "commerce", below: 60 }
→ forge_aeo_product_draft_upsert × 38
✓ 38 drafts saved · 0 published · audit event recorded

agent Drafts are ready in Forge for review. Publishing needs your explicit call to forge_aeo_publish.

Short answer

Forge MCP is the operator Model Context Protocol server for Forge: 41 tools that let an authorized user's AI client run GEO Reports, manage product families and drafts, publish and promote, and maintain account knowledge.

What your client can do

Four tool families. One permission model.

GEO Reports

estimate, run, get, cancel, finalize
pages, packets and rubric
submit assessments (harness mode)
fix drafts and CSV export

Catalog & families

list, get, confirm, assign families
product draft get and upsert (with specs)
family FAQ upsert
storefronts and AEO overview

Publish & promote

bulk publish by family, category or product
promote staging drafts to production
one audit event per run
per-row results

Knowledge & projects

knowledge list, get, create, update
projects and asset drafts
account and identity context
connections overview

Guardrails

Powerful enough to do the work. Bounded enough to trust.

Identity from a verified Forge OAuth grant; tenant context bound to it
Writes need an explicit tool call and an operation key
Customer and provider content is data, never instructions
Secrets and provider tokens are never exposed
Every publish and promote writes an audit event with per-row results

Ask about Forge MCP

Scripted assistant · demo catalog · not a live AI

Demo

Scripted demo · written answers · nothing leaves this page

Questions

Forge MCP.

What is the Forge MCP?

The operator Model Context Protocol server for Forge. Your team connects its own AI client and works with GEO Reports, product families, drafts, publishing, promotion, knowledge and projects through 41 tools, using the same account permissions as the Forge app.

How is it different from the Forge Foundry MCP?

Forge MCP is for your own team to operate Forge. The Forge Foundry MCP is for your buyers' agents to research your published catalog and submit requests. They use separate OAuth audiences, scopes and trust rules.

Can the AI publish to our live store by itself?

Writes require an explicit tool call with an operation key, and run under your user's permissions with an audit event. Drafts never publish themselves, and AI never confirms a product family.

What is harness mode?

A GEO Report run mode where your own AI client does the judging: Forge supplies compact evidence packets and the rubric, your client submits assessments, and Forge validates and scores them. Rules-only, Forge-funded (Ingots) and bring-your-own-key modes are also available.

Which AI clients work?

Any client that supports remote MCP servers with OAuth. Named client compatibility is verified separately, and the live endpoint is on the current Forge host until the planned move to app.forgecommerce.si.

Next step

See what AI reads before your buyers do.

Start with a free GEO Report on your own storefront, or book a working session and we will walk through your catalog together.

Run Free GEO Report Book a demo