Enzzo MCP

Connect your AI tools to Enzzo using the Model Context Protocol (MCP), an open standard that lets AI assistants interact with your Enzzo workspace.

Why this matters

Your Enzzo product data is only valuable if it's usable where your team already works. MCP closes that gap.

Enzzo stays the source of truth

Nothing changes about how you build and refine product information in Enzzo. MCP just opens a pathway out.

Works with tools you already pay for

No new software to learn. Connect the Enzzo catalogue to Claude, ChatGPT, or Microsoft Copilot.

Built for enterprise security

OAuth-based connection, read-only access at launch, and detailed logs for audit purposes.

Turns data into output, faster

Skip the copy-paste between systems: go from Enzzo product data straight to wireframes, journeys, and analysis.

What you can do with it

A few scenarios our early users are already running.

1. Design

   Generate a Figma wireframe from your product data

   Pull your Enzzo Dream product information directly into Figma to draft a device UI or connected-app wireframe — without re-typing specs or feature lists.

2. Journey mapping

   Build a visual user journey in Figma or Miro

   Turn your product structure into a user journey flow your team can review, edit, and share — grounded in the product you've actually defined in Enzzo.

3. Validation

   Stress-test a concept against real-world evidence

   If your company's other data is also reachable via MCP, query across DREAM project history, strategy review docs, interview transcripts, and support tickets to sharpen your product thinking before you commit.

Connect Enzzo in a few minutes

Setup differs slightly by platform — pick the one your team uses.

• Claude
  Step 1: Open Claude's connector settings. In Claude, go to Settings → Connectors (available on claude.ai and in Claude Desktop / Cowork).
  Step 2: Add the Enzzo MCP connector. Search for “Enzzo” or paste the Enzzo MCP server URL: https://app.enzzo.ai/api/mcp
  Step 3: Authorize with OAuth. You'll be redirected to sign in with your Enzzo workspace credentials and approve read-only access.
  Step 4: Start querying your product data. Ask Claude to pull Enzzo product info directly into a wireframe, journey map, or analysis.

• ChatGPT
  Step 1: Enable Developer Mode. ChatGPT support requires a paid plan with Developer Mode enabled in Settings → Connectors.
  Step 2: Add a custom connector. Choose “Add connector” and enter the Enzzo MCP server URL: https://app.enzzo.ai/api/mcp.
  Step 3: Authorize with OAuth. Sign in with your Enzzo workspace credentials and approve read-only access.
  Step 4: Bring Enzzo into any chat. Reference the Enzzo connector in a conversation to pull in your product catalogue.

• Microsoft Copilot
  Step 1: Your IT/admin team sets this up. Unlike Claude and ChatGPT, Copilot connections are configured centrally through Copilot Studio, not by individual users.
  Step 2: Admin registers the Enzzo MCP connector. Your admin adds Enzzo as a connector in Copilot Studio and sets the OAuth configuration.
  Step 3: Access is rolled out to your team. Once configured, approved users can query Enzzo product data directly inside Copilot.

Frequently asked questions

Does this change how I use Enzzo day to day?

No. You keep creating, refining, and saving product information in Enzzo exactly as you do today. MCP simply adds a secure pathway that other AI tools can read from.

Can the connected AI tools write back into Enzzo?

Not at launch. Access starts read-only. Any future write access would be a separate, explicit configuration.

Who can see what was accessed?

Every query through the MCP is captured in detailed audit logs, so your team can review exactly what was accessed and when.

Which platforms are supported today?

Claude and ChatGPT are user-configurable now (ChatGPT requires a paid plan with Developer Mode enabled). Microsoft Copilot is typically configured by your IT/admin team via Copilot Studio.

What if my company has its own internal data sources?

If your other systems (docs, transcripts, support tickets) are also reachable via MCP, you can query across them alongside your Enzzo data for deeper product validation.

Let's roll this out to your team

We'd love to walk through a live demo and build a rollout plan for your users.