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.
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.
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.
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.