ChatGPT

ChatGPT runs on OpenAI's infrastructure. There is no local client; OpenAI directly calls your MCP endpoint. Therefore, the server must be publicly accessible via HTTPS, with a certificate from a widely recognized CA. localhost, *.ddev.site, IP allowlists, and self-signed certificates do not work.

Authentication is done via OAuth 2.1 with Dynamic Client Registration. Custom connectors require a paid ChatGPT plan (Plus, Pro, Team, Business, or Enterprise); the free plan lacks the configuration interface.

Requirements

enableMcp is enabled (see Configuration).
mcpAllowedRedirectUris contains chatgpt.com/connector_platform_oauth_redirect.
mcpAllowedOrigins contains chatgpt.com.
mcpAllowedClientIds remains empty.
The backend group has enable_mcp_access and the required feature rights (see Permissions & Scopes).

Check the public accessibility from a machine outside your network. Both calls must return 200:

curl -sS [typo3-url]/aisuite-mcp/healthcurl -sS [typo3-url]/.well-known/oauth-authorization-server

If an IP allowlist, HTTP Basic Auth, or a self-signed certificate blocks either of the two paths, the connection fails without a useful error message. If the installation is behind Basic Auth, the MCP paths must be excluded; see Production Operation. Also, ensure that the Authorization header reaches PHP; otherwise, endless 401 responses will follow after a successful OAuth flow.

Set Up Connection

1. Open Connector Settings. Log in to chatgpt.com and open the Settings via the profile icon in the top right corner, then go to Connectors. Depending on the plan, the section may also be called Apps & Connectors.

2. Create Connector. Select Add custom connector, enter a name (for example, AI Suite), use [typo3-url]/aisuite-mcp as the MCP server URL, and select OAuth for authentication. Use only the root URL without site prefix.

3. Connect and Agree. After Connect, ChatGPT registers at [typo3-url]/aisuite-mcp/oauth/register and opens the authorization page. There, the TYPO3 backend login follows, and then the consent page with the requested scopes. After confirmation, the connector shows Connected.

4. Activate Connector per Conversation. Start a new chat, click the + icon below the input field or Tools, and enable AI Suite. Only then will the tools be visible to the model.

You can end access either in ChatGPT by removing the connector or in the TYPO3 backend via the MCP dashboard with Revoke Token.

Connector or Deep Research

This guide describes the custom connectors of ChatGPT. Only this method provides the model with the full tool scope of the AI Suite MCP, including reading, writing, generating, translating, images, and batch processing.

The separate deep research connectors from ChatGPT are something else. They only call two tools named search and fetch according to OpenAI's convention. The AI Suite MCP deliberately does not register these two names, as they would otherwise appear in every other MCP client. Therefore, the AI Suite MCP cannot be used as a deep research source. For content work, use the normal connector. The closest reading equivalents are searchContent, readPageContent, and readRecords, which the model can call directly in the normal chat.

Troubleshooting

Nothing happens when clicking Connect, and nothing is logged in TYPO3. The server is unreachable from OpenAI's network, or the certificate is not recognized. Check the two curl calls from an external machine.

The model claims it has no MCP access, even though the connector is connected. The connector is not enabled in the current chat; see step 4.

The tool list remains empty. The backend user lacks the AI Suite feature rights. Add rights and re-authenticate in the connector.

No logs are viewable on the ChatGPT side. The access log of the web server is significant. A 404 on /aisuite-mcp indicates a site prefix issue, while repeated 401 responses indicate a missing Authorization header. Other client-independent cases are collected under Connect Clients.