Taufinity Studio

Appearance

Connect ChatGPT to Taufinity Studio ​

Status: coming soon

ChatGPT Custom Connectors require OAuth 2.1 with Dynamic Client Registration. Taufinity Studio's OAuth Authorization Server is on the roadmap (Track 3). This page documents the flow that will be live once Track 3 ships.

What's coming ​

Once OAuth ships, the connection flow will be:

  1. In ChatGPT → Settings → Connectors → Add custom connector.
  2. Paste your org's connector URL: https://studio.taufinity.io/mcp/<your-org-slug>.
  3. ChatGPT redirects you to Taufinity Studio's consent screen: "ChatGPT wants access to <Your Org>: read your data, modify your data."
  4. Approve, and ChatGPT is connected — no manual token paste, no manual config file.

Config file location

  • macOS: ChatGPT app → Settings → Connectors → Add custom connector
  • Linux: ChatGPT (web) → Settings → Connectors → Add custom connector
  • Windows: ChatGPT app → Settings → Connectors → Add custom connector

Option 2: Manual install — paste this snippet

https://studio.taufinity.io/mcp/<your-org-slug>

Notes

  • ChatGPT Custom Connectors require OAuth 2.1 + Dynamic Client Registration. Track 3 ships these endpoints; until then, this page documents the expected flow.

Why OAuth (and not bearer paste)? ​

ChatGPT requires Dynamic Client Registration (RFC 7591) and PKCE (RFC 7636) to register a connector. Taufinity Studio is implementing both — see the design spec for the architecture.

For other clients today, bearer-token paste is fine because the user controls the local config file. ChatGPT runs in OpenAI's infrastructure and cannot accept user-pasted tokens.

How to get notified ​

  • Existing customers: your implementation partner will let you know when ChatGPT support is live.
  • Prospects: email [email protected] and ask to be added to the launch list.

See also ​