Flowstate in ChatGPT

Same MCP server. Different chat client. Flowstate exposes one MCP server; both Claude.ai and ChatGPT install against it. This page covers the ChatGPT Connectors install path.

Prerequisites

Before you start:

• Your org must have the mcp_external_access feature toggle enabled. If it's off, contact Flowstate support — it's gated per-tenant.
• You need a ChatGPT Enterprise (or Team) admin role with permission to add connectors org-wide.
• You need a Flowstate user account with the permissions you want the connector to inherit.

Install

The connector URL Flowstate exposes is the same one Claude.ai uses:

https://{tenant}.flowstate.inc/api/mcp

In ChatGPT's Connectors settings:

1. Add a new MCP-based connector.
2. Paste the connector URL above (replacing {tenant} with your subdomain).
3. ChatGPT initiates OAuth — Flowstate hosts a consent page asking which scopes to approve.
4. Approve. ChatGPT stores the access + refresh tokens.

The OAuth flow is identical for both clients: dynamic client registration (RFC 7591), PKCE (S256), JWT access tokens (1 hour), opaque refresh tokens (30 days, rotated on each refresh).

Tool catalogue

Identical to the Claude install. Read tools work without a scenario; write tools require an explicit planId from a prior create_scenario call. There's no client-side difference — the same MCP tools surface in either chat.

Permissions

The MCP server inherits the OAuth user's Flowstate permissions. The connector cannot do anything the user can't do in the UI.

Rate limiting

Same as Claude: 100 requests per minute per user with X-RateLimit-* headers and JSON-RPC error code -32000 when exceeded.

Audit and SIEM

Every MCP request emits a SIEM event regardless of which chat client made the call. If your org has SIEM integration configured, ChatGPT-driven MCP traffic appears in the same stream as Claude-driven traffic, distinguishable by the OAuth client name.

Disabling

Org-wide: ask Flowstate support to flip mcp_external_access off.

Per user: revoke the OAuth grant from Settings → API Keys.

Reference

For the protocol-level details — OAuth endpoints, token schema, transport, full tool catalogue — see API → MCP server.