Connect ChatGPT
ChatGPT connects to your site as an MCP client through a custom connector. The process is the same as with Claude: a URL, OAuth authorisation, and your site's tools appear in the conversation.
Prerequisites
Custom connectors (MCP servers) use ChatGPT's developer mode, which is available on the Plus, Pro, Team, Enterprise and Edu plans; the free plan does not support them. In a Team, Enterprise or Edu workspace, the administrator must first allow the creation of custom connectors (Workspace settings → Permissions and roles).
On the site, Senso MCP 1.2.12 or later is required. Versions 1.2.0 to 1.2.11 accept ChatGPT's connection but do not present it with any tools (see Troubleshooting).
Create the connector
In ChatGPT on the web, open Settings → Apps → Advanced settings and enable developer mode. Then create a connector by entering:
- a name, for example your site's name;
- the MCP server URL:
https://your-site.tld/api/index.php/v1/mcp(see Server endpoints). Use the site's canonical domain, with or withoutwwwaccording to your Joomla configuration: this is the address that the Senso MCP dashboard displays as the server address; - authentication: OAuth. You do not need to enter client credentials, as ChatGPT obtains them automatically from the discovery documents published by your site.
ChatGPT connects exclusively via OAuth: a Joomla API token cannot be used with it. The token and the “Client configuration (JSON)” section in Settings are intended for other clients, such as Claude Desktop, Claude Code or n8n.
Authorise the site
An authorisation page opens on your site. Sign in with a Joomla account that has the required permissions, choose the scopes granted to this connection, then confirm. No password is sent to ChatGPT: only an access token is issued, which can be revoked at any time from your site.
Once authorisation is complete, the connector details in ChatGPT list the tools exposed by your site. If this list is empty, see Troubleshooting.
Use the connector
Connectors are disabled by default in each new conversation. Open the + menu in the input field, then enable your site's connector: its tools will then be made available to the model. You can issue your first command, for example “list the latest published articles”. As with any client, the site's switches, the account's ACL and the granted scopes determine what ChatGPT can do.
Troubleshooting
ChatGPT stops before the authorisation page. ChatGPT cannot find your site's connection settings. Open Senso MCP → Settings: if the “OAuth sign-in” card is orange, click Repair automatically. This is typical of hosting providers that respond to /.well-known/ addresses themselves, such as SiteGround (see Connection troubleshooting). Also check that a firewall or security extension is not blocking ChatGPT user agents (openai-mcp/1.0.0, openai-connectors-oauth/1.0).
Authorisation succeeds, but ChatGPT cannot see any tools. The model says that the connector does not exist, or refers to missing “plugins”. This behaviour occurs with Senso MCP versions 1.2.0 to 1.2.11: ChatGPT first sends a discovery probe (server/discover, MCP protocol 2026-07-28), and these versions responded in a way that prevented it from continuing with the standard negotiation (initialize), so it never requested the list of tools. Update the site to 1.2.12 or later, then, in ChatGPT, open the connector and restart authorisation: there is no need to delete it. The tools appear immediately.
The tools are listed in the connector details, but the model does not use them. Check that the connector is enabled in the current conversation (the + menu), and that developer mode is still active in Settings. If necessary, start a new conversation.
Check on the site. The Senso MCP dashboard logs every MCP request. A healthy connection from ChatGPT leaves the sequence initialize, notifications/initialized and then tools/list. If the log shows only authentication entries and nothing else, the site is not up to date.
Official documentation
- Developer mode and MCP apps in ChatGPT — OpenAI Help Center