Shared /mcp: ChatGPT connections get multi-step and connector tools - #844
Merged
Merged
Conversation
The shared endpoint now picks its tool set from the OAuth client a token was issued to. Clients registered with a chatgpt.com or openai.com redirect URI get the eight shared tools plus anythingmcp_run_read_steps, anythingmcp_find_connectors, anythingmcp_add_connector and anythingmcp_connection_status, with readOnlyHint, destructiveHint and openWorldHint set on every tool. Every other client, API keys and any caller whose client cannot be resolved keep the eight tools exactly as the Claude directory reviewed them.
…wers OpenAI does not allow a plugin to promote upgrades or link to a page that starts one. On the ChatGPT tools the setup answer drops connectorsLeftOnThisPlan and upgradeUrl, and a connector limit is explained without pointing at billing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
OpenAI rejected the AnythingMCP plugin (v1.0.0, 29 Sep) because it "mainly relays third-party integrations without standalone value or a meaningful workflow". A comparable gateway is listed in the ChatGPT Plugins Directory with first-class tools for multi-step work and connection management. This gives ChatGPT connections the same kind of tools, without touching what the Claude directory reviewed.
What
The shared
/mcppicks its tool set from the OAuth client the access token was issued to (azp→oauth_clients.redirect_uris, cached):chatgpt.com/openai.com, https only): the eight shared tools plusanythingmcp_run_read_steps: up to 10 read-only tools in one call, run in parallel, per-step results; every step goes through the read runner, so writes, payment connectors and other workspaces stay outanythingmcp_find_connectors,anythingmcp_add_connector(write, not destructive),anythingmcp_connection_status: the existing setup service as first-class tools; always listed, refused with a dashboard link for callers who may not install connectorsreadOnlyHint,destructiveHintandopenWorldHintset explicitly on every tool (OpenAI's review requires all three)Production check:
oauth_clientshas 3,226 Claude registrations (claude.ai/api/mcp/auth_callback) and 57 ChatGPT ones (chatgpt.com/connector_platform_oauth_redirect,chatgpt.com/connector/oauth/…).Tests
profileForRedirectUris: ChatGPT/OpenAI hosts, Claude, native schemes, look-alike hosts, http, junk[]on missing client or DB errorFull backend suite: 6,658 passed.