ChatGPT can run your Gmail shared inbox through one custom connector, on every plan including Free. The verified six-step setup, the permission prompts to expect, and what to ask first.
Key takeaways
- Connect ChatGPT to your shared inbox in one pass: turn on Developer mode (Settings, then Security and login), create an app from the Plugins screen with https://app.dragapp.com/mcp as the server URL, sign in with Drag, and enter your API key once on Drag's own page.
- It works on every ChatGPT plan, including Free, verified September 2026. There is nothing to install, no configuration file, and nothing to restart.
- Expect two safety screens and welcome both: Developer mode shows a red ELEVATED RISK notice because it accepts unverified connectors, and ChatGPT then asks permission before every action that changes your inbox, with Deny, Allow once, or Always allow.
- Drag connects as a custom connector you add yourself. It is not a directory listing or a partnership; the connector gives ChatGPT 47 tools across 12 categories, from listing boards to sending replies, always under your permission prompts.
Table of contents
Connect ChatGPT to your Gmail shared inbox and the queue becomes something you can talk to: show me today's unread threads, draft replies to the urgent ones, assign the rest. The whole setup happens inside ChatGPT's own settings, works on every plan including Free, and was verified end to end in September 2026: connector created, boards listed, a real email sent.
Under 30 seconds, if you have done this before: ChatGPT › Settings › Security and login › Developer mode on › sidebar › Plugins › Create app › Connection = Server URL, paste https://app.dragapp.com/mcp, Authentication = OAuth › Create › Sign in with Drag › enter your Drag API key (DragApp › Settings › Integrations) on the page that opens. Done.
One honest sentence before the steps, because it is the part most guides hide: ChatGPT will show you a red warning on the way in. That is by design, it applies to every custom connector from any company, and this guide tells you exactly where it appears and what it means, so nothing on this path surprises you.
This is what the connection buys you. One chat, working a real morning queue:
Morning. What's waiting on the Support board?
7 unread. Three need you first:
1. "Order #4821 - shipping damage" · Sarah Mitchell URGENT
2. "Refund not received" · Maya Torres BILLING
3. "API rate limit increase" · DevOps Team ENGINEERING
The other four are newsletter replies and can wait.
Draft replies to the first two in our tone, assign the API one to Marcus, and label everything.
Two drafts ready for your review, written against your help center's shipping-damage and refund articles. The API thread is assigned to Marcus and labeled Engineering.
For Maya's refund, check Stripe for her last payment and put the exact amount in the draft.
Found it: $49.00 on July 28. Draft updated to confirm a $49.00 refund, arriving in 3 to 5 business days.
And how did we do last week?
Average first reply 2h 14m, 18% faster than the week before. Tuesday was the slow day.
One chat, two connectors: Drag for the inbox, Stripe for payments. ChatGPT asked before each action that changed anything: Deny, Allow once, or Always allow.
The Stripe step works because connectors stack: create Stripe's connector alongside Drag's the same way, and ChatGPT uses both in the same conversation. The rest of this guide gets you to that point.
Before you start
Three terms cover all the theory. MCP (Model Context Protocol) is the standard that lets AI tools plug into other software, and Drag runs an MCP server for your inbox. A custom connector is what you are creating in ChatGPT: you give it a web address, and everything behind that address becomes tools ChatGPT can use, with your permission. Your Drag API key is the code that proves the connection is yours, which is why ChatGPT can only ever see what your Drag account can see. Deeper background, if you want it: MCP for customer support.
You need two accounts:
- A ChatGPT account, on any plan. We verified the whole flow on a Free account in September 2026: Developer mode toggled, connector created, boards listed, email sent.
A DragApp account with your shared inbox set up, on a plan with API access.
One thing to know going in: Drag connects to ChatGPT as a custom connector that you add yourself. There is no directory listing and no partnership, and this guide never pretends otherwise. The custom route is the official, supported way ChatGPT connects to any MCP server, and it is the same door tools of every size use.
Using Claude instead? Its connector setup is three steps in a different place: the Claude guide covers it, along with the config-file route for Cursor, Claude Code, and Windsurf.
How to connect ChatGPT to your shared inbox
Step 1: Turn on Developer mode
In ChatGPT, open Settings, go to Security and login, and scroll down to Developer mode. Toggle it on.
The toggle carries a red ELEVATED RISK badge reading "Allows you to add unverified connectors that could modify or erase data permanently." Read that as what it is: ChatGPT's standard warning for every custom connector, from any company, because Developer mode accepts servers OpenAI has not reviewed. Two things keep you in control on the other side of it. You choose exactly one server to add, at an address you copied from this page. And ChatGPT asks before every action that changes anything, which Step 4 shows you.
Step 2: Create the connector
In the sidebar, open Plugins. With Developer mode on, a Create app button appears next to the search box (it is absent until the toggle is on, which is the quickest way to tell the mode took effect).
Click it, and fill in the New Plugin dialog:
- Name: Drag (any name works; this is what the permission prompts will show)
- Description: optional
- Connection: Server URL
- URL:
https://app.dragapp.com/mcp - Authentication: OAuth
Tick the risk acknowledgment and click Create.
Step 3: Sign in with Drag
ChatGPT shows a consent screen: "Add Drag to ChatGPT." Click Sign in with Drag.
Drag's own connect page opens and asks for your API key, once. Copy it from DragApp under Settings, then Integrations, paste it in, and submit. The key is entered on Drag's page, never in a web address, and never shown to ChatGPT itself; the connection carries your permissions and nothing more.
Step 4: Confirm it, and meet the permission prompt
Back in a chat, ask:
The first time ChatGPT uses a Drag tool that changes anything, it stops and asks. The prompt names the app, describes the action in plain English, lists the data being shared, and offers three buttons: Deny, Allow once, or Always allow. Each connector also has a Permissions setting, defaulting to "Allow low-risk actions," which you can tighten or loosen per app.
This is the part worth pausing on, because it is the answer to the red badge in Step 1: Developer mode opens the door, and the permission prompts guard everything on the other side of it. Reading your queue is low-risk and flows freely; sending a reply from your shared inbox happens only after you have seen, in plain English, what is about to be sent and approved it.
You're connected: what to ask first
Start with the read-only sweep every team runs first:
ChatGPTReply, using Drag's MCP toolsWhat happens underneath: ChatGPT calls list_threads and get_thread on your board, the same tools every request on this page uses, and none of that needs a permission prompt because reading is low-risk by default.
Then let it act, and approve what you see:
ChatGPTChatGPTThat send is where the write gate appears: ChatGPT shows you the reply and the recipient, and reply_to_thread runs only after you allow it.
For the weekly rhythm:
ChatGPTChatGPTMore where these came from: the AI prompt library has nine pages of prompts that run on a connected inbox, including a ChatGPT-specific collection.
Drag AI
The inbox your team and your AI work in together
Shared inbox, live chat, and AI in Gmail, with an MCP server your AI tools can drive.
What you can do once connected: 47 tools across 12 categories
list_threads · get_thread · reply_to_thread · send_new_email · search_threads · filter_threads · move_thread · move_threads_bulk
list_cards_in_column · get_card · create_card · update_card · move_card · archive_card
list_boards · get_board · list_columns · list_board_members · list_teams
list_articles · get_article · create_article · update_article · search_knowledge
get_response_times · get_avg_response_time · get_daily_activity · get_closed_activity
list_labels · add_label_to_thread · remove_label_from_thread · toggle_labels
get_whatsapp_conversation · list_whatsapp_templates · send_whatsapp_message · send_whatsapp_template
list_automations · toggle_automation · toggle_ai_drafts
search_contacts · get_contact_conversations · create_contact
add_comment · get_comment
list_tags · add_tag_to_card
create_task
Troubleshooting
No Create app button on the Plugins screen. Developer mode is not on. It lives under Settings, then Security and login, and the button only appears after the toggle is enabled.
The consent screen never opens. Check the Connection type is Server URL and the address is exactly https://app.dragapp.com/mcp, then create the app again. Typos in the URL fail silently at this stage.
The key is rejected on the connect page. Copy it fresh from DragApp under Settings, then Integrations. Keys are account-specific, so the Drag account that owns the key is the account ChatGPT will act as.
Tools worked yesterday and are missing today. Open the connector under Plugins and check its Permissions setting; if the connector was removed, recreate it, and the same key works again.
A write you expected never happened. Look for the permission prompt: if it was denied, or is still waiting, the action did not run. ChatGPT reports success only after the tool call completes.
Frequently asked questions
Does connecting Drag to ChatGPT work on the free plan?
Yes. We verified the full flow on a Free ChatGPT account in September 2026: Developer mode toggled on, the connector created, boards listed, and an email sent from the shared inbox. If OpenAI changes plan availability later, the dated claim here is the one to check against.
Is Developer mode safe to turn on?
The red ELEVATED RISK notice is ChatGPT's blanket warning for unverified connectors, and it is worth taking seriously as a habit: only add servers from companies you trust, at addresses you copied from their own pages. The mode itself changes nothing until you add a connector, and every connector you do add sits behind ChatGPT's per-action permission prompts and a per-app Permissions setting.
Can ChatGPT send email from our shared inbox?
Yes, with your approval. Send and reply tools are gated: before the message goes, ChatGPT shows what it is about to send and to whom, and offers Deny, Allow once, or Always allow. Teams that want a human on every send simply never choose Always allow for the send tools.
How is this different from ChatGPT's built-in Gmail connector?
The built-in connector links your personal Google account for reading and drafting in your own mail. The Drag connector puts ChatGPT on your team's shared inbox: boards, assignment, labels, replies sent from the shared address, and response-time reporting, 47 tools in all. The full comparison of the routes lives in Connect Gmail to ChatGPT.
Is Drag listed in ChatGPT's app directory?
No. Drag connects as a custom connector you add yourself by URL, the official route ChatGPT provides for MCP servers outside its directory. Nothing about the connection is unofficial; the directory is a separate distribution channel, not a requirement.
Does this work in Claude, Cursor, or other AI tools too?
Yes, the same server connects to any MCP-capable client. Claude adds it as a custom connector in three steps, and config-file tools like Cursor, Claude Code, and Windsurf run it locally via the npm package: the Claude guide covers both routes.
Related guides: the wider connector landscape
The Connect Gmail to ChatGPT guide compares all three routes to your email, including the built-in connector this page is not about. What happened to ChatGPT plugins explains how the plugin era became connectors and MCP. For choosing tools beyond email, the best ChatGPT connectors for email and best ChatGPT plugins and connectors survey the field. And when the connection is live, the AI prompt library is the fastest way to put it to work.
Co-founder
Building Drag for nearly ten years: shared inboxes, boards, and now the AI and agent layer, all on Gmail, plus HeyHelp for the personal inbox. Writes the honest versions of the comparisons.
