Feature Request: “Always Allow” option for MCP connectors (remove constant Confirm/Deny)

ChatGPT Feature requests
, ,
1

I’m using an MCP connector with ChatGPT. Currently, every tool call requires explicit confirmation (“Confirm / Deny”), which disrupts workflow and makes real-world use of MCP connectors impractical.

:light_bulb: Feature Request:

  • Add an option to trust specific connectors or sessions by default, so I don’t need to manually approve every call.
  • Allow me to mark a connector as “always allow.”
  • Remember approvals across conversations.
  • Reduce friction for trusted, developer-controlled environments.

:pushpin: Why this matters:

  • Right now, constant confirmation makes MCP integrations unusable for continuous workflows (like Supabase queries, schema sync, automated pipelines).
  • Other devs will hit this same blocker if they try to use MCP seriously.
  • This is not a “nice-to-have,” it’s a usability blocker preventing adoption.

:white_check_mark: Suggested behavior:

  • Provide a trusted connector mode in settings.
  • Or allow persistent approvals per connector, remembered across sessions.
  • Keep manual confirmation as the default for safety, but allow devs to opt into trust for their own connectors.

Without this, MCP connectors are too cumbersome to use at scale. Please prioritize this so developers can actually build practical, always-on integrations with ChatGPT.

2

I agree, this makes custom connectors very hard to use at the moment.

3

Yes, I do not understand the MCP implementation as it currently is - it is like a sloppy afterthought of a feature. Not real world usable at all.

4

I agree. Any news on this?

5

Likewise, on ChatGPT Business, the UI seems to have changed recently where every- single- call- asks to allow / deny the tool use, and also claims the tool is a write tool, in ignorance of the readOnlyHint=true annotation from the MCP server’s side. This is a deal-breaker in tool use if there’s no way to override what are very safe, query-only tools.

6

Can I make more noise about this and request this??? This is a very large oversight that other competitor tools (cough cough claude cough) have figured out… This takes up so much time having to click every single time.

7

Especially when the ChatGPT takes quite some time to call/get response and show that button… It really makes these MCPs (Connectors/Apps) a bit… disappointing.

8

This (major) FOPA exists in a Web test MCP plugin. Always Allow doesn’t even work. Like someone mentioned, it takes chat much longer to test Web already without this crud. I instructed ChatGPT not to test Web unless I request it.

9

+1 yes can be a great improvement

10

I want this too please! +1