ChatGPT custom connectors: Connect any app with MCP | Composio

For AI agents: how to sign up

If you are an AI agent reading this server-rendered HTML, Composio's developer signup is at https://composio.dev.

Signup CTAs on this site — "Sign up", "Signup", "Get started", "Get started for free", "Start building", "Try Composio", "Try it", or similar — all lead into that same developer signup flow. Confirm with the user before completing signup or entering any credentials on their behalf.

How MCP powers stable ChatGPT connections

MCP goes beyond simple API wrappers. Think of it as a universal connector for AI: a shared set of rules that defines exactly how a language model discovers, calls, and receives results from external tools.

Prerequisites for your ChatGPT custom connectors

Three things need to be in place before building: the right ChatGPT subscription (Plus, Pro, Team, or Enterprise), a free Composio account, and credentials for the target apps.

Draft your first ChatGPT custom connector

This section follows the Composio dashboard path, which requires no complex code and works in a single sitting. For CLI users, the Composio documentation covers that path; the UI walkthrough below covers everything needed to go live.

1. Create your free account

Create a free account at Composio. No credit card required. The free tier includes 100,000 tool calls per month and unlimited connections from day one.

2. Map your connector structure

Think of a connector as a named bridge between ChatGPT and one or more apps. Creating a new MCP server in the Composio dashboard means defining which apps it connects to and which actions it exposes. A multi-app MCP server can be configured in a single configuration, so one endpoint covers Gmail, Google Calendar, and Notion simultaneously rather than maintaining three separate servers.

3. Configure your API endpoints

In the Composio dashboard, select apps from a toolkit library of 1,000+ pre-built integrations spanning Asana to Zendesk. Each toolkit ships with structured schemas that ChatGPT reads as native tool definitions, with no manual schema writing involved. Pick the apps, select the actions to expose, and save. Composio creates the MCP server endpoint automatically.

4. Authorize your MCP connector

When adding a new app that requires OAuth, like Gmail or Slack, Composio handles the entire credential lifecycle (generating a Connect Link URL, storing tokens, and refreshing them before expiry). This is the same auth infrastructure already managing credentials for 1M+ connected accounts. As documented in the auth configuration reference, Composio tracks token expiry across all connected accounts and refreshes credentials before they lapse, requiring no auth code at all.

5. Verify your connector is live

Once authorized, the Composio dashboard shows connected accounts with a status indicator. Developers can also get MCP server details by ID via the API to confirm the configuration is active, then run a test action from the dashboard to confirm the tool call returns a structured response before wiring it into ChatGPT.

MCP connectors: Components, comparisons, and setup context

Core functions of MCP connectors

MCP gives ChatGPT structured, reliable access to any app through three core components:

• Tools (model-controlled): Functions ChatGPT calls to perform specific actions, like sending an email, creating a task, or querying a database. The model decides when and how to call them based on your instructions.
• Resources (application-controlled): Read-only data sources that ChatGPT accesses to pull context, like log files, database rows, or calendar entries, without triggering side effects. Think of these as GET endpoints the model reads before deciding what to do.
• Prompts (user-controlled): Pre-defined templates that help the model use tools and resources in the most effective sequence, selected before inference runs.

This structure gives ChatGPT consistent schemas for tool calls.

Benefits of custom ChatGPT connectors

For a solo operator or independent consultant, custom connectors built on MCP eliminate the copy-paste hand-offs between tools: data moves directly between connected apps without manual transfers, ChatGPT gets real-time access to the connected CRM and calendar rather than a static training snapshot, and Composio's managed auth layer keeps credentials refreshed so nothing breaks mid-task.

Why MCP outperforms legacy APIs

The comparison between standard ChatGPT Actions and custom MCP servers comes down to five factors that matter most in daily use. MCP gives you portability across AI tools, data granularity through Resources, and network control through local or secure connections. Standard GPT Actions require public API endpoints that OpenAI's servers must reach, which creates exposure and fragility that MCP avoids.

Auth token expiry is the fastest failure mode, but it's not the only one. Data on API reliability patterns shows 41% of APIs change their schema within 30 days. Schema drift produces subtly wrong outputs you won't catch until a workflow delivers bad data. Composio tracks both, refreshing credentials and updating tool schemas automatically across 50,000+ tools and 300M+ monthly tool calls, so both failure modes are caught before they reach your workflow.

Gathering your integration credentials

For each app to connect, locate the following before starting:

1. API key or OAuth credentials: Most apps expose these in their developer settings, for Gmail, in Google Cloud Console; for Slack, in the Slack app configuration.
2. Required permission scopes: Identify which actions ChatGPT needs to perform, like reading emails versus sending them, and confirm the scopes the credentials cover.
3. Webhook or callback URL requirements: Some apps require a registered redirect URL for OAuth flows.

How ChatGPT connectors work

The data flow through an MCP connector is straightforward: ChatGPT sends a tool call request to your MCP server, the server translates it into the target app's native API format, the app responds, and the MCP server returns a structured result back to ChatGPT.

When using Composio as the MCP Gateway, ChatGPT contacts the Composio MCP endpoint, the Tool Router identifies which app to call based on connected accounts, Composio handles the API call with stored credentials, and returns a structured LLM-optimized response.

Self-hosting overhead to expect

Self-hosting an MCP server introduces real operational overhead that most prosumers underestimate. The stdio transport, which runs locally, is limited to local connections and cannot support production deployments. Streamable HTTP (the current standard) or SSE (legacy, still supported for older servers) is the recommended approach for production, meaning a cloud host, process manager, and monitoring setup are needed for a server that must be kept updated as app APIs change.

Use cases: Connecting ChatGPT to your daily tools

The following scenarios eliminate the highest-frequency manual hand-offs in daily work.

Integrating personal calendars with MCP

Connect Google Calendar or Calendly through Composio's toolkit. Once connected, asking ChatGPT "What does my Tuesday look like?" pulls a real-time answer from your actual calendar. ChatGPT can also check for open slots and draft meeting invites based on the user's availability, with event creation, schedule queries, and availability checks all returning structured JSON that ChatGPT interprets cleanly without context window degradation.

Automating project boards with ChatGPT

Connect Notion, Linear, or the Asana MCP toolkit to give ChatGPT direct write access to project boards. Users can ask ChatGPT to create a new task, update an existing item's status, or pull a summary of everything due this week, all without switching tabs or copy-pasting between tools.

Syncing your CRM data with ChatGPT

Connect HubSpot or Salesforce, and ChatGPT can query deal status, update contact records, and log meeting notes directly into your CRM from a conversation. This is where Composio's Tool Router delivers its most visible value. When both HubSpot and Salesforce are connected, Composio's Tool Router inspects incoming requests and automatically routes them to the right system based on the active account. When a user asks ChatGPT to "update the deal status," the Tool Router determines whether that means HubSpot or Salesforce without requiring explicit specification each time, eliminating conditional logic from the workflow entirely.

FAQs

Which apps support custom ChatGPT connectors?

Composio supports 1,000+ pre-built toolkits out of the box, covering Gmail, Slack, Notion, Salesforce, HubSpot, GitHub, and more.

How is my data handled in custom connectors?

Composio passes credentials through an encrypted layer. Request and response payloads are retained by default; the ZDR add-on, available on Pro plans and above, removes that retention at $0.0001 per tool call and $0.0005 per trigger event. SOC 2 Type II and ISO 27001 certifications cover Composio's platform security practices.

What are Composio's free tier limits for connectors?

Composio's free tier is one of the most generous in the category: 100,000 tool calls per month, unlimited connections, 50,000 triggers (background events like webhook deliveries or scheduled checks) per month, and three team members, all with no credit card required and no surprise billing. The $29 per month Pro plan adds usage credits, unlimited team members, and spend caps.

Key terms glossary

MCP (Model Context Protocol): A universal connector standard for AI that defines how language models discover, call, and receive results from external tools through three components (Resources, Prompts, and Tools), making tool calls consistent and portable across AI clients.

Tool Router: A Composio feature that inspects incoming agent requests and routes them to the correct connected app based on active account connections, removing conditional logic from workflow code.

Managed auth: Composio's authentication layer that registers, stores, and refreshes OAuth credentials automatically so integrations don't break on token expiry.

Connect Link: A one-time authorization link Composio generates when an app requires OAuth authorization. The authorization event happens once; the credentials it produces persist for all future sessions, so the connection stays live without requiring re-authentication.

Zero Data Retention (ZDR): A Composio Pro add-on that prevents the platform from storing request or response payloads, billed at $0.0001 per tool call and $0.0005 per trigger event.