ChatGPT MCP server: add a custom connector

A ChatGPT MCP server exposes external tools that ChatGPT can discover and call through the Model Context Protocol. Current OpenAI setup documentation adds a custom MCP server through Plugins; “custom connector” remains a common search term for that connection. AIPx supplies a public OAuth-protected agent URL with scoped access to connected services.

Can ChatGPT use MCP servers?

Yes, supported ChatGPT workflows can use remote MCP tools. The relevant question for setup is whether your account and workspace expose the custom-server installation interface. That is separate from whether the server implements a compatible protocol or whether an upstream account grants access to its data.

A server advertises operations, including their input schemas, then receives calls chosen during a conversation. ChatGPT does not gain every capability of an application’s website just because its account is connected. It gets the tools exposed by the server and allowed for the authenticated connection.

With AIPx, ChatGPT connects to an agent endpoint, while AIPx connects to your service accounts. You can allow reads for a work account, confirm writes and hide a personal account. The integration’s underlying provider access remains a further boundary. A successful ChatGPT login cannot grant privileges the provider account lacks.

For the term itself, see what an MCP connector means. For another conversational client, the Claude connection guide explains its different menus and configuration.

Add an MCP server to ChatGPT as a custom connector

The current interface documented by OpenAI uses Plugins. If an older tutorial tells you to look for “Connectors,” compare its date with the current MCP server quickstart before following the menu labels.

1. Connect the intended service accounts in AIPx.
2. Create a ChatGPT agent, assign its accounts and review its tool rules.
3. Copy the personal endpoint, such as https://dash.aipx.run/mcp/AGENT_ID, with your actual identifier.
4. In ChatGPT, open Plugins, use the plus button and choose Add custom MCP server.
5. Enter the server name and URL and configure its authentication. Use the OAuth route for AIPx.
6. Review the connection notice and create the plugin.
7. Install it, start a chat and select the plugin with @plugin as documented by the interface.
8. Try one known read and compare the result with the source service.

The URL identifies an agent; it is not a secret that substitutes for authentication. Completing OAuth for ChatGPT’s connection to AIPx does not replace the earlier service-account connection in AIPx. Keep the two sign-ins distinct when diagnosing a failure.

No local JSON configuration is required for this hosted installation path. A claude_desktop_config.json example from another client does not configure ChatGPT. Hosted clients also cannot reach your laptop’s localhost without explicit routing. Use the public HTTPS AIPx endpoint rather than a local development address.

Which ChatGPT plans support custom connectors

Check the feature in your current account and workspace before purchasing a plan for this setup. The official material reviewed for this page establishes the custom-server workflow but does not establish a complete plan entitlement table. It would be misleading to infer that every Free, Plus, Pro or organizational account has the same installation rights.

The current pricing and account guidance and your workspace settings are the relevant checks. Organizational administrators may restrict custom server installation or use. A missing menu can therefore be an account or policy limitation rather than a malformed MCP endpoint.

Check	Why it matters	What to verify
Account interface	Installation rights can vary	Add custom MCP server is available
Workspace policy	Administrators can constrain external access	The server is allowed for your workspace
Server compatibility	A URL alone does not prove a valid connection	Supported transport and authentication
AIPx plan	Account and agent limits are separate	Free or Pro fits your connected accounts
Service account	Provider privileges remain in force	The account can perform the requested operation

AIPx Free and ChatGPT’s subscription are different products. Paying for one does not upgrade the other or remove a service provider’s API limits.

Give ChatGPT scoped access with AIPx

Choose the permission boundary around a real conversation. A meeting assistant might read work mail, calendar events and notes, while a billing assistant needs a narrower financial context. Putting every account into one general-purpose agent makes it harder to explain why a particular result was available.

AIPx applies Allow, Confirm and Hide per tool, account and agent. Allow and Confirm are execution hints; Confirm asks the client to request approval. Verify the actual client behavior. Hide is enforced server-side and removes access for that agent. Different accounts of the same service can have different rules, so work Gmail can be available while personal Gmail is hidden.

An outgoing message deserves confirmation, but a read deserves a confidentiality check too. Mail threads, documents and spreadsheet rows can contain sensitive material that will become conversation context. Restrict the account and operation to what the task actually needs.

The confirmation should match the intended recipient, account and content. It is not a rollback mechanism and cannot guarantee that an approved action is wise. ChatGPT controls its own approval behavior. AIPx Confirm supplies an approval hint, while Hide provides the enforced server-side removal boundary.

AIPx records account, agent, tool, inputs, result and time in a shared audit. Inspect the first calls to verify the chosen account and operation, especially if several similarly named accounts are connected. The MCP permissions guide expands that decision process, while the gateway guide explains how one connected account can serve multiple agents.

Connect your tools to ChatGPT

For a different conversation, the following supported services provide additional development, infrastructure or personal context. Their account privileges and provider costs remain independent of ChatGPT installation.

• Development and infrastructure: Sentry error reports, PostHog analytics, Atlassian Rovo tools, Supabase project tools, Cloudflare account tools, DigitalOcean infrastructure.
• Mail, notes and planning: Apple Calendar access, Things 3 tasks, Fireflies transcripts, AgentMail inbox tools.
• Payments: Paddle subscription tools.
• Research and campaign data: Exa web search, Google Maps data, X account tools, Yandex Direct campaigns.
• Personal health and nutrition: WHOOP recovery data, Withings measurements, Hevy workouts, Numon nutrition reports.

These choices fit conversational tasks without assuming every tool should be enabled. The server selection guide has a wider catalog and deployment comparison.

Integration	Useful first request	Suggested boundary
Gmail	Summarize a named work thread	Confirm outgoing operations; hide personal mail
Google Calendar	Read tomorrow’s relevant meetings	Keep account and calendar selection explicit
Google Sheets	Inspect a small planning table	Confirm edits to existing data
Notion	Find a project decision	Review the connected workspace
GitHub	Explain an issue discussion	Confirm shared repository changes
Stripe	Investigate a specific billing question	Restrict financial actions
Linear	Retrieve a task brief	Confirm creation and updates
Confluence	Find a supporting technical document	Review accessible spaces
Granola	Consult meeting notes	Treat private meeting content as sensitive
Jira	Read acceptance criteria	Limit the connected account scope

Troubleshooting a ChatGPT connector

If installation is unavailable, check the account and workspace feature first. If the authentication step fails, verify the agent URL and AIPx account. If login succeeds but a provider call fails, reconnect the upstream service account. If tools are missing, inspect AIPx Hide rules and refresh the installed connection’s discovery before broadening access.

A direct official integration can be simpler for one service. AIPx adds another hosted operator and needs network and upstream API availability; it is useful when several accounts need consistent rules across clients. Free includes three connected accounts and one agent. Pro is $3 per month with unlimited accounts and agents plus Pro integrations. Connect free.