Fractall's connector is one MCP server, and MCP is what ChatGPT uses for connectors too. Once the hosted endpoint is live, pointing ChatGPT at it is the same job as pointing Claude at it. There's nothing to connect today.
Nothing to show yet: no ChatGPT connector has been built
The connector would run on MCP, an open standard for giving an assistant access to a system, and it's the same server the Claude connector uses. That's the reason this doesn't need building twice. The tools that read your teams and athletes don't care what's asking. When the endpoint is hosted, the work left for a second client is configuration rather than a rebuild.
One server
The same read-only tools serve any MCP client.
Read only and club scoped
The same limits apply, whatever connects.
Configuration rather than a rebuild
Adding a client isn't a second product.
No ChatGPT connector exists in the product. The server it would run on is partly built, the hosted endpoint isn't, and Claude is the client we're building against first. This page is here so you know where ChatGPT sits rather than assuming it's covered.
Not built
No ChatGPT connector, in any form.
Not scheduled
We'll quote a date when we have one worth quoting.
Claude first
That's the client the current work targets.
If ChatGPT is what your staff already have open, that's worth knowing, and it moves the client order. Say what you'd ask it too, because that decides which tools get built first.
Early access
We'll come to you when there's something to connect.
Client order
Which assistant your staff use is what sets the priority.
Tell us which assistant your staff already use and we'll factor it into the order.