Connect Flowstate to ChatGPT

Connect ChatGPT to Flowstate when you want to ask things like "what's our AI spend by team this month?" in ChatGPT and get the answer from your Flowstate data. ChatGPT acts as you: it sees only what you can see in Flowstate, and changes only what you can change.

You need MCP access switched on for your organisation. Ask your Flowstate contact.

Before you start

• In ChatGPT: you need to be able to add a custom connector, which uses ChatGPT's developer mode. On a ChatGPT workspace, an admin may need to allow it.
• In Flowstate: you need your own account. Everyone signs in as themselves; there's no shared connection.

Connect

1. In Flowstate, select Ask Eddy in the top bar.
2. Select New chat (the +) to see Eddy's starting screen.
3. Under Connect from Claude or ChatGPT, select Copy MCP URL. It's your Flowstate address followed by /api/mcp/protocol, for example https://acme.flowstate.inc/api/mcp/protocol.
4. In ChatGPT, open Settings → Connectors and add a custom connector (developer mode).
5. Paste the MCP server URL as the server URL.
6. When the Flowstate page opens, sign in with your Flowstate account if asked, then select Approve.
7. Start a new conversation and ask a question about your Flowstate data. If ChatGPT doesn't use Flowstate, check the Flowstate connector is turned on for the conversation.

What you can ask

• "What's our AI spend by team this month?"
• "Who joins the Platform team next month, and what will they cost?"
• "What is the Payments team working on right now?"
• "Which projects are completed but still have people on them?"
• "How far has the forecast moved from the budget we locked?"
• "Show me the functional structure under Engineering, with open seats."
• "Create a scenario that moves Priya to the Data team from next month."

Name the team, project or person as it appears in Flowstate, and say the period you mean.

What ChatGPT can change

ChatGPT can do the same things as Claude.

In a scenario. When you ask ChatGPT to add, move or remove people, teams, vacancies, contractors, projects, allocations, budgets or AI agents, it makes a new scenario (or uses one you name). Nothing reaches live data until someone submits, approves and merges that scenario in Flowstate. See Live data and scenarios.

In live data, straight away. These apply as soon as ChatGPT makes them:

• budget requests and proposals: create, cancel, assign, submit, approve, reject and comment
• initiatives, objectives and key results
• CapEx claims and capitalisation records
• functional groups, their seats and managers
• which project your own AI sessions count towards

Not at all. ChatGPT can't approve or merge a scenario, lock a budget, or do anything your Flowstate role doesn't allow.

Tip

Before ChatGPT changes live data, ask it to tell you what it's about to do, and check it names the right team, project or person.

The full list of what ChatGPT can call is in the tool catalogue.

If something's not right

There's no Connect from Claude or ChatGPT box in Eddy. MCP isn't switched on for your organisation. Ask your Flowstate contact.

You can't add a custom connector in ChatGPT. Developer mode is off, or your workspace admin hasn't allowed custom connectors. Ask your ChatGPT admin.

"MCP external access is not enabled for this organization". MCP has been switched off for your organisation. Ask your Flowstate contact.

"User is inactive or not a member of this organization". Your Flowstate account has been deactivated or moved to another organisation. Ask a Flowstate admin, then connect again.

ChatGPT says you don't have permission. Your Flowstate role doesn't allow it. Ask a Flowstate admin.

"Rate limit exceeded. Try again shortly." You've made too many requests in a minute. Wait a minute and ask again.

Disconnect

In ChatGPT, open Settings → Connectors and remove the Flowstate connector. ChatGPT connections don't appear on Settings → Users & Access → API Keys in Flowstate.

If you don't use it, ChatGPT stays signed in for up to 30 days before you need to approve it again.

For your technical team

• The connector uses OAuth 2.0 with PKCE and dynamic client registration, over MCP Streamable HTTP. There's no API key.
• Every request is recorded as an audit event, and reaches your SIEM if you've connected one.
• For endpoints, token lifetimes and errors, see MCP server → For developers.