ChatGPT Apps vs Connectors vs MCP Servers, Explained (2026): What Each One Is and Which to Add First

Key Takeaways

• For creative planning, add Storyflow first: one address (https://mcp.storyflow.so/mcp) lets ChatGPT, Claude, Gemini and Grok build boards, tables, documents and slide decks in the projects you pick, and read back what changed and who changed it.
• An MCP server is the thing a company runs. A connector, an app or a plugin is what your assistant calls that server once you add it. The protocol underneath is the same in all four assistants.
• ChatGPT renamed connectors to apps on December 17, 2025, then replaced its app directory with a plugin directory in July 2026. A plugin bundles apps (MCP connections) with skills (reusable instructions).
• A custom connector is any MCP server you add by its URL instead of picking it from a directory. ChatGPT calls the switch for this developer mode; Claude calls it Add custom connector; Gemini calls it a custom app; Grok calls it a Custom connector.
• Claude's Free plan allows one custom connector. Storyflow's own setup guide lists ChatGPT Plus or above, with developer mode on, for adding a custom MCP server in ChatGPT.
• Permission is the real decision, not the name. Before you sign in, decide which projects, whether the assistant may write, and how you will disconnect it.
• Gemini asks you to confirm every write action today; Claude shows a tool approval request and offers Allow always per tool; OpenAI tells developers to require confirmation for irreversible actions.
• Storyflow is paid-only during early access and its MCP server launched in October 2026, so it has the shortest track record on this list. Anyone a paid member invites joins free and gets 25 MCP actions a week.

Why the Names Keep Changing

You read a setup guide from March, open ChatGPT, and the menu it describes is gone. That is not you. In under three years OpenAI has used four names for the same idea, and the other assistants each picked their own. Here is the sequence, so the old guides make sense.

2023 to 2024: the first ChatGPT plugins

The original ChatGPT plugins of 2023 were a separate system with their own store. OpenAI shut them down in spring 2024, and nothing from that store carried over. If a guide mentions a plugin store with a manifest file and an OpenAPI spec, it is describing that retired system.

November 2024 onward: MCP becomes the plumbing

Anthropic published the Model Context Protocol as an open standard for connecting assistants to outside systems. The MCP introduction describes it as "like a USB-C port for AI applications": one plug shape, many devices. In December 2025 Anthropic donated MCP to the Agentic AI Foundation, a fund under the Linux Foundation co-founded with Block and OpenAI, and the announcement counted more than 10,000 active public MCP servers. That is why one server now works in ChatGPT, Claude, Gemini and Grok.

December 17, 2025: connectors become apps

OpenAI's Apps in ChatGPT article records the rename: chat connectors became "apps with file search", deep research connectors became "apps with deep research", and synced connectors became "apps with sync". Nothing had to be reconnected. Some apps also draw an interactive interface inside the chat, which is where "app" stops being only a rename.

July 2026: apps live inside plugins

In July 2026 ChatGPT's app directory became a plugin directory at chatgpt.com/plugins. OpenAI's Plugins in ChatGPT article defines a plugin as a bundle: apps connect to outside services, and skills hold reusable instructions, so a plugin can contain either or both. Existing connections kept working. The word "plugin" is back, but it means a package of MCP connections and instructions, not the 2023 plugin store.

The Seven Terms, Defined in One Sentence Each

Most confusion comes from mixing up who runs a thing with what your assistant calls it. Each definition below names one side of that line.

MCP server

An MCP server is the service a company runs that tells an assistant which tools exist (for example "list my projects" or "create a table"), what each tool needs, and what it returns. Storyflow's runs at https://mcp.storyflow.so/mcp; Notion's runs at mcp.notion.com/mcp. You never open it in a browser; your assistant talks to it.

Connector

A connector is the assistant-side link to an outside service. Anthropic's connector docs say a connector "links Claude to an outside app or service", and that developers build one by building an MCP server. Grok also says connector. ChatGPT said connector until December 2025.

App

In ChatGPT since December 2025, an app is a connection to a service, sometimes with an interactive interface drawn in the chat. In Gemini, an app is the same idea under Connected Apps. When a vendor says "our ChatGPT app", they mean their MCP server, listed in OpenAI's directory.

Plugin and skill

In ChatGPT since July 2026, a plugin is an installable bundle of apps and skills. A skill is a set of reusable instructions with no outside connection of its own, such as "write the weekly update in this format". OpenAI's developer guide to packaging a plugin shows the same split: MCP server connections in one place, skills in another.

Custom connector (developer mode, custom app)

A custom connector is any MCP server you add by pasting its URL, rather than picking it from a vetted directory. Every assistant warns you here, because nobody at OpenAI, Anthropic, Google or xAI has reviewed that server. Storyflow is added this way in all four.

MCP App (interactive connector)

An MCP App is a connector that returns a small interactive interface, drawn in a sandboxed frame inside the conversation, instead of only text. The MCP Apps overview lists Claude and Claude Desktop among the clients that render them. Storyflow's show_board tool uses this to show the live board inside clients that support MCP apps.

Desktop extension (local MCP server)

A desktop extension is an MCP server that runs on your own computer rather than on the web. Anthropic packages these for the Claude desktop app only. They suit local files and developer tools; for a shared project board you want a remote server, which works on the web, desktop and mobile app once added.

ChatGPT vs Claude vs Gemini vs Grok: How Each Names and Handles Connectors

The same Storyflow address goes into all four assistants. What changes is the menu, the plan you need, and who has to switch it on. All details below are from each vendor's own documentation as of October 9, 2026.

Sources: OpenAI's custom MCP server steps, Anthropic's custom connector guide, Google's custom apps help page, xAI's Grok connectors docs and xAI's connector management page.

How We Ranked the Connectors Worth Adding First

Most "best connector" lists rank by how many tools a server exposes. That rewards size, not usefulness. For creative planning the question is narrower: once the assistant has thought the project through, where does the plan land, and can the people who need it open it? We built Storyflow's MCP server and connected it to Claude, ChatGPT, Gemini and Grok while writing the setup steps, then read every competitor's own documentation for the rest. The ranking uses six criteria, weighted for a founder, marketer or creative lead planning client or launch work.

How the scores add up

Each connector gets a 1 to 10 score per criterion; the rating is the weighted sum. Storyflow scores 10, 9, 9, 9, 7 and 5 for 8.5 (8.45 before rounding). Miro scores 7, 8, 6, 7, 9 and 8 for 7.4. Notion scores 7, 6, 7, 7, 7 and 9 for 7.1. Canva scores 6, 8, 6, 6, 6 and 9 for 6.9. Claude's Google Workspace connectors score 4, 5, 8, 8, 9 and 10 for 6.8. Figma scores 5, 6, 6, 5, 7 and 8 for 6.0. Storyflow loses maturity by the widest margin on the list; it wins the two criteria that carry 45% of the weight.

What we did not weigh

• Raw tool count. A server with 80 tools is not better than one with 30 if you only need five.
• Coding workflows. Figma's server is excellent for turning designs into code; that job has its own ranking.
• Email and calendar actions. They matter, but they are not planning, so Google Workspace ranks on its planning value here.

Connectors Worth Adding First, Ranked

Six connectors cover most creative planning work. Add them in this order, and stop when the next one solves a problem you do not have.

1. Storyflow

The verdict: the connector that turns a conversation into a visual project board other people can open.

Best for: founders, marketers and creative leads who think a project through in ChatGPT or Claude and need the plan to exist somewhere their team or client can see.

Pricing: Plus $7.99 a month billed annually ($9.99 monthly), Pro $14 ($19 monthly), Max $39 ($49 monthly). No MCP limit on any paid plan, and the server runs on your assistant's model, so it does not spend Storyflow AI credits. Storyflow is paid-only during early access; a Free plan launches before the end of 2026, and anyone a paid member invites joins free today with 25 MCP actions a week.

Why it ranks first: the familiar approach is to plan in a chat thread, then copy the answer into a doc, then rebuild it as a board for the team. Each copy loses structure. Storyflow's server skips both copies. Ask ChatGPT to "turn this launch brief into a board with the plan, the tasks and the open questions" and it calls create_project, then build_section, and the groups land on the board where they belong. Ask for a ten-slide deck from that board and create_deck puts it next to the plan. Ask "what changed on the launch board this week, and who changed it?" and get_board_changes answers from the board's own history. One address works in Claude, ChatGPT, Gemini, Grok, Claude Code, Cursor, VS Code with GitHub Copilot, Gemini CLI, Codex, Devin, Figma, Zed, Raycast, Lovable, Perplexity and Le Chat.

Strengths:

• Builds notes, groups, tables, charts, diagrams, mind maps, documents, slide decks, shot cards, strip boards, colour palettes and carousel pages, and applies board templates.
• Scope is chosen at sign-in: all projects or picked ones, read-only or with changes, and whether documents outside projects are included.
• Disconnect in Settings, Connected apps, and access ends within a minute; every connection also expires after 30 days.
• What the assistant adds appears live on a board you have open, and show_board displays the board inside clients that render MCP apps.

Limitations:

• Launched October 2026: the shortest track record and the smallest template ecosystem on this list.
• Paid-only during early access.
• Browser only: no native mobile or desktop app, no offline mode.
• A photo you attach in the chat does not reach Storyflow; request_photo_upload gives you an upload link instead.

Try it: connect it from the Storyflow MCP page, or follow the step-by-step help article.

2. Miro

The verdict: the strongest board connector for teams already living in Miro.

Best for: product and workshop teams whose boards are already in Miro.

Pricing: Miro's MCP server page says it works on all Miro plans, even free teams.

Why it ranks here: Miro's server can summarize and search boards, build boards, generate diagrams and act on comments, and its documented clients include Claude, ChatGPT and Codex, Claude Code, Cursor, Gemini CLI and VS Code. That is real build capability on a visual surface, which is why it ranks second. It ranks below Storyflow on this job because Miro's documentation describes no per-project scope choice at sign-in (the server follows your existing board permissions), and because Miro is a whiteboard rather than a planning workspace: there is no built-in path from the board to slide decks, shot cards or strip boards for production work.

Strengths:

• Free-plan access.
• Diagram generation from a description.
• Mature product with a large template library.

Limitations:

• No per-project scope choice described at sign-in; it follows your existing board permissions.
• Enterprise workspaces carry extra admin security controls to check first.

3. Notion

The verdict: the right connector when your plans already live in Notion pages and databases.

Best for: teams with a Notion wiki, content database or project tracker.

Pricing: Notion's MCP help page states no plan requirement for basic connections; admin approval of AI apps is an Enterprise feature.

Why it ranks here: Notion runs a hosted MCP server at mcp.notion.com/mcp that lets assistants such as Claude, ChatGPT and Cursor read from and write to your pages. Writing a plan into a Notion page is useful and reliable. It ranks third because a page is a document: the assistant can write the plan, but a client or a crew cannot read the shape of a project at a glance the way they read a board.

Strengths:

• Hosted server with OAuth sign-in.
• Reads and writes pages and databases your account can reach.
• Enterprise owners can restrict which AI apps members connect.

Limitations:

• Output is text-first.
• Notion's page lists ChatGPT under "ChatGPT Pro", so check which ChatGPT plan you need.

4. Canva

The verdict: the connector for the finished asset, not the plan.

Best for: marketers producing social graphics and decks from templates.

Pricing: Canva's documentation and help centre disagree on which Canva plans include the connector, so check Canva's AI connector setup page against your own account.

Why it ranks here: Canva's AI Connector lets ChatGPT and Claude create designs, autofill templates, find existing designs and export them as PDF or image. That is the last step of a campaign, which is why it sits fourth. Plan the campaign on a board, then ask the assistant to produce the twelve assets in Canva.

Strengths:

• Design output from your own templates.
• Export to PDF or image from the chat.

Limitations:

• No project plan, timeline or task layer.
• Plan eligibility is unclear between Canva's own pages.

5. Google Workspace (Gmail, Calendar, Drive) in Claude

The verdict: the inputs connector: files, mail and dates.

Best for: anyone whose briefs, contracts and call notes sit in Drive and Gmail.

Pricing: Anthropic's Google Workspace connectors page says they are available to all users on Claude and Claude Desktop.

Why it ranks here: Claude can search and read Docs, Sheets, Slides and PDFs in Drive, draft and send mail, and create or update Calendar events. By default it asks your approval before sending, sharing, moving or trashing. It scores top on maturity and permission control but low on building a plan, because the output is a file or an email rather than a project. ChatGPT has its own Google Drive app; OpenAI says app availability varies by plan and region, and Grok lists Gmail, Calendar and Drive among its built-in connectors.

Strengths:

• Free in Claude.
• Approval before the risky actions.
• Pulls the source material a plan needs.

Limitations:

• Not a planning surface.
• Embedded images and attachment contents have limits.

6. Figma

The verdict: essential for design-to-code, marginal for planning.

Best for: designers and developers moving between Figma files and code.

Pricing: your Figma plan rules apply; the remote MCP server guide covers setup.

Why it ranks here: Figma's remote server at mcp.figma.com/mcp works from links: you paste a file or layer link so the assistant knows what to read. Writing to the canvas is limited to some clients, such as Claude Code, Codex and VS Code. That makes it a strong developer connector and a weak planning one.

Strengths:

• Reads exact design context from a link.
• Hosted remote server.

Limitations:

• Link-driven, so it does not browse a project for you.
• Canvas writing is client-limited.

Not on the list: Milanote

Milanote is a common answer for moodboards, and we checked for it. We found no official Milanote MCP server, ChatGPT app or Claude connector as of October 9, 2026. If you plan in Milanote, your assistant cannot read or build those boards today.

Safety and Permissions: What You Actually Grant When You Connect

You click Connect, a sign-in page appears, and thirty seconds later an AI can act in your account. Most people never read that page. These five questions decide whether the connection is safe, regardless of what the assistant calls it.

Read or write: the only switch that really matters

A read-only connection can leak information but cannot damage anything. A write connection can create, edit and move things. Storyflow asks at sign-in whether the assistant may make changes; without that, it only reads. Start read-only for a week on a live client project, then reconnect with changes on.

Scope: which projects, which team, which files

Storyflow lets you pick all projects or named ones, and asks whether documents outside projects are included; that option starts on when you allow all projects and off when you pick projects. Miro follows your existing board permissions. Notion reaches what your account can reach. Narrow is safer: pick the two projects you are working on, not all forty.

Prompt injection: the risk you cannot see

A web page, a document or a tool description can carry hidden instructions. Anthropic warns that "malicious MCP servers may include hidden instructions that try to make Claude perform unintended actions." OpenAI's security guidance for app builders tells developers to "assume prompt injection and malicious inputs will reach your server." It is not the assistant you need to trust. It is every server and every document the assistant reads while it holds write access.

Confirmation: who asks before acting

Gemini says it "requires manual confirmation for any write actions." Claude shows tool approval requests and offers Allow always; Anthropic's advice is to choose it only for a server and tool you trust to run unsupervised, and to switch off write tools before running Research, which can call connector tools without asking. OpenAI tells app builders to require human confirmation for irreversible operations.

Revocation and expiry: how you get out

Storyflow also shows an "I trust this app" warning when an app it does not recognise asks to connect, and you tick it before you can continue.

Worked Example: A Product Launch Brief Turned Into a Board From ChatGPT and Claude

Theory only goes so far. Here is one illustrative job, run end to end. The brand, budget and call count are an example, not a measurement.

The brief

A two-person skincare brand is launching a cleanser in six weeks. The founder has a 900-word brief in a Google Doc: three audiences, one hero claim, eight deliverables (a 30-second film, six social posts, one landing page), a $6,000 budget, and four open questions about retail partners. Until now she pasted the brief into ChatGPT, got a strong plan back, and then spent an hour turning that plan into tasks for her designer.

The setup: about five minutes, once

She turns on developer mode in ChatGPT, adds Storyflow at chatgpt.com/plugins with the Public endpoint option, signs in to Storyflow, picks the one project she wants it to use, and allows changes. Her designer, who works in Claude, adds the same address as a custom connector and connects read-only. Two assistants, one board, two different permission levels.

The run: nine actions

She pastes the brief and asks: "Build a Storyflow board for this launch with the plan by week, the tasks by owner, the budget table and the open questions." A clean run looks like this:

Assistants sometimes split or repeat calls, so treat nine as the floor for this job, not a promise. On Plus, Pro or Max there is no MCP limit. On a free invited account, 25 actions a week is room for this board and a few follow-up questions, with the count resetting Monday UTC.

What changed

The plan no longer lives in a chat thread nobody else can see. Her designer opens the board by link, reads the tasks under her name, and asks Claude "what is still open on the launch board?" without being able to change the budget. The connector did not make the plan better. It made the plan exist in a place two people could use. For the planning method itself, see the best AI tools for founders and the AI project plan generator.

How to Connect Storyflow in Each Assistant

All of these use one address: https://mcp.storyflow.so/mcp. Storyflow speaks Streamable HTTP, not SSE. The full guide, with screenshots, is the Connect Claude, ChatGPT and Other AI Tools help article.

Claude (web and desktop)

1. Open Customize, then Connectors.
2. Click Add, then Add custom connector.
3. Name it Storyflow, paste the address and click Continue.
4. Choose Sign in now, click Add, and sign in to Storyflow, picking projects and whether it may make changes.

On Claude's Free plan this uses your one custom connector. On Team and Enterprise an Owner adds it first under Organization settings.

ChatGPT (web)

1. Open Settings, then Security and login, and turn on Developer mode. On Business and Enterprise an admin does this.
2. Go to chatgpt.com/plugins and click the plus button.
3. Name it Storyflow, choose Public endpoint and paste the address.
4. Review the risk warning, create it, and sign in to Storyflow.

ChatGPT needs Plus or above for this, per Storyflow's setup guide, and the setup runs in ChatGPT on the web.

Gemini app

1. On gemini.google.com, open Settings, then Connected Apps.
2. Under Custom apps, click Add a custom app.
3. Paste the address, click Next, and sign in to Storyflow.
4. In a prompt, type @ and choose Storyflow.

You need a personal Google account with Keep Activity on, in the US, aged 18 or over, in English.

Grok

1. Open grok.com/connectors and click New Connector, then Custom.
2. Paste the address and sign in to Storyflow.

On Grok Business and Enterprise, an admin adds the connector in the xAI console first, then members connect their own accounts.

Claude Code and other developer tools

In a terminal, run: claude mcp add --transport http storyflow https://mcp.storyflow.so/mcp, then type /mcp inside Claude Code and sign in. Cursor, VS Code and Gemini CLI each take the same address as a remote HTTP server in their own MCP settings. For tools that cannot run a sign-in, Storyflow issues a personal key that lasts 30 days.

Prompts You Can Copy Once Storyflow Is Connected

These work in ChatGPT, Claude, Gemini and Grok. Name the connector in the prompt the first time; assistants pick the right tool more reliably when you do.

For a full month of content done this way, see the AI content calendar guide and the AI content planner.

What It Costs: Assistant Plan Plus Connector

A connector is rarely the expensive part. The assistant plan that allows custom connectors is. Prices below are monthly, in USD, from each vendor's own page as of October 9, 2026.

Sources: Claude pricing, ChatGPT Plus and Storyflow pricing. Grok says connectors are available to all Grok users; we did not verify a current Grok price on xAI's own page, so it is left out.

Where the real cost is

The real cost is not the $8 to $30. It is the hour a week spent turning a chat answer into something a team can act on. If the connector removes that hour, the price is noise. If you only ever ask questions and never share the result, Claude Free with Google Drive is enough, and you should stop there.

Decision Rules: App, Connector or Raw MCP Server?

The name on the menu does not matter. Which door you use does, because each door has different vetting and different defaults.

Use the directory version when one exists

If a service is listed in ChatGPT's plugin directory or Claude's Connectors Directory, use that listing. It has been through the vendor's review, and Anthropic labels listings as Verified or Community. Google Workspace and Canva both offer directory routes in Claude.

Use a custom connector for anything new or niche

Services that launched recently, including Storyflow, are added by URL. That is normal, not a red flag on its own. Check that the address is on the vendor's own domain and that the sign-in page is theirs.

Use a local server only for local things

If the data lives on your laptop (a folder of scripts, a local database), a desktop extension or a local MCP server is right. For anything a team shares, use a remote server so it works on the web, desktop and mobile app.

Use the assistant your team already pays for

One MCP server works in all four assistants, so the connector should not decide your assistant. If the founder uses ChatGPT and the designer uses Claude, both connect to the same board.

Common Mistakes When Adding Connectors

Every one of these comes from a real setup that went sideways. All are cheap to avoid.

Mistake 1: Allowing everything on the first sign-in

All projects, write access and documents outside projects, on day one, for a server you have not used. Start with one project, read-only.

Mistake 2: Clicking Allow always on write tools

Claude's Allow always is convenient for reads. For tools that create, move or delete, keep the prompt until you trust the server's behaviour.

Mistake 3: Following an older ChatGPT guide

If a guide says Settings, Connectors, Advanced, Developer mode, it predates the July 2026 move to plugins. Use Settings, Security and login, then chatgpt.com/plugins.

Mistake 4: Expecting a pasted photo to reach the board

Images you attach in a chat stay in the chat. Storyflow's request_photo_upload tool hands you a link to upload to the board instead.

Mistake 5: Forgetting connections expire

Storyflow connections end after 30 days and the assistant asks you to sign in again. That is a safety feature. Put a monthly reminder in the calendar rather than reaching for a long-lived key.

Mistake 6: Using Research or deep research with write tools on

Anthropic notes that Research can invoke connector tools without further approval. Switch write tools off before a long autonomous run.

When Storyflow Is Not the Right Choice

Storyflow ranks first for one job: turning an assistant's plan into a visual board other people use. For these jobs, pick something else.

You need a free setup today

Storyflow is paid-only during early access. If you need $0, use Claude Free with the Google Workspace connectors, or Miro's server on a free Miro team.

Your plans already live in Notion

If your team's projects, wiki and content database are in Notion, moving the plan to a board adds a second home. Connect Notion's server and keep one source of truth.

You need finished designs, not a plan

For twelve social graphics on brand, Canva's connector produces the assets. Storyflow plans the campaign; it does not lay out your final Instagram post.

You need offline or native apps

Storyflow runs in the browser only. There is no native desktop or mobile app and no offline mode.

You need publishing, invoicing or formal approvals

Storyflow does not publish or schedule social posts, does not send call sheets or track confirmations, has no approve button for versioned sign-off, and does not do invoicing or contracts.

You weigh track record above everything

Storyflow's MCP server launched in October 2026. If years in market is the deciding factor, Google Workspace, Notion and Canva have the longer records.

Template: A Connector Audit You Can Copy

Run this once a quarter, or before you add a new connector. It takes ten minutes and catches most of the risk.

The audit table

The five questions per row

1. Do I still use it weekly? If not, remove it.
2. Is the scope the smallest that does the job?
3. Does it need write access, or would read-only do?
4. Is the server on the vendor's own domain?
5. Who else on the team has the same connection, and do they need it?

The Bottom Line

App, connector, plugin and MCP server are four labels for one idea: a service your assistant can read and act in, built on an open protocol that works across ChatGPT, Claude, Gemini and Grok. Stop sorting by the label. Sort by the job. For creative project planning, add Storyflow first, connect it read-only to one live project for a week, then allow changes and let the assistant build the board, the deck and the weekly change report. Add Google Workspace for the source material, Notion if your plans are documents, and Canva for the final assets. If you only ever ask questions and never share the answer, you do not need a planning connector at all. If the plan has to reach a team or a client, connect Storyflow from the MCP page and turn your next brief into a board.