For general MCP setup (Claude, ChatGPT, Cursor, and other clients), see the main Scribe MCP Server help center article. This page covers what's specific to Optimize.
Optimize connects to AI tools through the same Scribe MCP server used by Capture - enabled by default, read-only, and scoped to your Optimize role.
Is Optimize MCP a separate server?
No. There's a single Scribe MCP server (https://mcp.scribe.com/mcp) for both products. "Optimize MCP" just refers to the workflow and insights data that server exposes once your org has the Optimize module - not a different connection or endpoint. If you have both Capture and Optimize, the same connection surfaces both.
How to connect
The server is hosted by Scribe - nothing to install. Authentication is automatic OAuth 2.0: your browser opens, you sign in with your Optimize credentials, and you authorize the client.
Claude Code:
claude mcp add --transport http scribe https://mcp.scribe.com/mcp
Claude Desktop: Customize → Connectors → Settings → Developer Settings → Edit Config, then add:
{
"mcpServers": {
"scribe": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.scribe.com/mcp"]
}
}
}ChatGPT: Developer Tools → Add MCP Server → Server URL https://mcp.scribe.com/mcp, Authentication: OAuth. Requires ChatGPT Business, Enterprise, or Edu with Developer Tools access.
Cursor: Settings → MCP Servers → Add Server, or add to .cursor/mcp.json:
{
"mcpServers": {
"scribe": { "url": "https://mcp.scribe.com/mcp" }
}
}Copilot Studio: Tools → Add a tool → New tool → Model Context Protocol → Server URL https://mcp.scribe.com/mcp → Authentication: OAuth 2.0 → Create.
Windsurf: edit ~/.codeium/windsurf/mcp_config.json — uses serverUrl instead of url.
VS Code (GitHub Copilot): Command Palette → "Preferences: Open User Settings (JSON)" → add the same URL under mcp.servers.
Admins can turn this off org-wide at Settings → Developer Access → Enable MCP Server Connection (on by default).
What Optimize adds to the connection
- Workflows: explore the business processes Optimize has discovered, navigate the hierarchy from value chains down to individual tasks, review execution history, apps used, and time-on-task.
- Insights: AI-detected friction points and optimization opportunities, filterable by severity, with recommendations.
- Cross-source search: search across documents (if you have Capture too), workflows, and insights at once.
Example prompts: "Where are the bottlenecks in our workflows?" · "Show me the workflow hierarchy for Sales Operations."
Permissions
Data is scoped to your existing Optimize role - Team Optimizers only see their team's data; Org Optimizers see all teams. Same admin-approved app whitelist and redaction settings apply.
How this overlaps with Scribe MCP (Capture)
Optimize and Capture share one MCP connection and one admin toggle (Settings → Developer Access). The difference is eligibility, not infrastructure: Capture requires Enterprise Grid or Global for MCP access, while every Optimize customer gets it regardless of tier. Because both products currently share the same backend entitlement flag, an org with Optimize + a lower Capture tier (e.g. Hub) may find MCP also surfaces Capture data — this is a known, temporary gap rather than a supported feature, and shouldn't be relied on.