Same issue. The MCP server registers and tools are recognized but greyed out. And when ChatGPT is searching for the tools its returning empty list
1 Like
Same here.
However, if I hit refresh on tools I do get server responses. But only chatgpt can’t initialize tools
1 Like
Seeing the same issue. Tools that have worked previously are no longer available. When adding as a connector I can see server-side that the tools are being fetched and on the ChatGPT connectors UI I can see the tools however they are greyed out.
Same issue here. Seeing greyed out tools on Pro accounts, and no tools pulled at all on Business account. Below for screen shots.
Also want to note that this MCP works fine in Playground + Agent Builder
PRO
Curious. Are any of the MCP’s you are using require auth? I tried passing in an access token and custom headers but I get a 424 when looking at the console. I managed to connect an MCP server that does not require Auth and it worked in the Agent Builder preview - tools were showing and agent successfully called them. It failed a few times with an error response code after running for a while though. So things are definitely flaky.
Still not working, the problem has appeared for two days. Works well on Claude.
1 Like
Same issue here. On Pro account. Connector creation works, it lists my tools, but they are grey’d out and cannot be called successfully within conversation. Server logs suggest GPT isnt making any server calls.
I am seeing the same issues. I know my mcp server is good, it works in all other valid mcp clients. It works in the openai playground as well. I even tried the apss sdk example app directly. they all load, but chatgpt can’t ever find any tools. it is able to find tools for oficially published apps like spotify, but dev server mcps are no longer working. dev servers inside chatgpt have been flaky for quite a while, but now I am seeing that it is not working at all. Hopefully this gets resolved soon.
Follow-up summary (for OpenAI team visibility):
Several developers (myself included) are continuing to experience the same issue with custom MCP connectors inside ChatGPT.
Confirmed working elsewhere:
Custom MCP servers run fine in the OpenAI Playground and other valid MCP clients.
Handshakes, manifests, and tool registration complete successfully.
Broken inside ChatGPT:
Tools appear in the list but are greyed out / non-invokable.
Only officially published connectors (e.g. Spotify, Zapier) remain enabled.
The Deep Research “search/fetch” protocol is still visible, suggesting the regression is on ChatGPT’s MCP trust or enablement layer.
This looks like a client-side regression — possibly in the tool-enablement or trust-validation step — rather than a schema or server issue.
Multiple users (including @bradybenware and @Peter2002) have confirmed the same pattern. Peter summed up the reality well:
> “My boss is angry with me because he doesn’t believe there’s an issue with OpenAI. When do you anticipate this issue will be resolved, @OpenAI team?”
At this point, a few clarifications would really help the dev community:
1. Is ChatGPT’s MCP runtime being modified to restrict custom connectors to “trusted” or “approved” ones only?
2. If this is a temporary regression, what’s the ETA for restoration or an official fix notice?
3. Can OpenAI confirm whether custom MCPs will continue to be supported going forward?
We’ve all verified the issue reproducibly — live servers, manifest exports, and log traces can be shared privately if needed for debugging.
An official acknowledgment (even a brief “we’re aware and investigating”) would go a long way toward preventing confusion and internal fallout for devs relying on custom MCP workflows.
1 Like
Same issue here. Tools are listed when connecting in Developer mode but no tools can be invoked.
There’s a comment on a github thread (which I can’t link to …) acknowledging the issue.
Cross posting for visibility — Repo is openai/openai-apps-sdk-examples issue #1
2 Likes
Thanks for sharing this!
It’s a shame they couldn’t keep their “community” in in the loop, and there’s a not-so-subtle irony in their “Next Big Thing” being affected right after roll-out when they had days of heads-up from devs.
1 Like
sheesh, I’ve been pulling my hair out and screaming at Claude for the last 24 hours, trying to figure out what broke on my end 
2 Likes
I think you owe something an apology 
Can anyone confirm if it’s working for them yet? I’m still hitting the same issue.
at my end in team plan, no tool listed and not appear in dropdown in the chat…
Not for me - the only “change” is that now search and fetch are also greyed out and missing their toggle. The fact that the sdk repo says it’s fixed and will be rolled out in the next deploy (2 hours) - confirmed for me something a little bit scary - they actively roll out changes regularly without any sort of QA or thorough testing.
That explains why a refresh can suddenly change/break stuff in realtime.
its not the first time they broke something…
do you have a team plan or just pro/plus ?
because i have team plan but i dont have advanced setting or developer mode…
I’m on Plus - it was pretty awesome when they rolled it (Custom MCP) out, then over a short period of time they neutered it daily with Developer Mode, Memory Off, introducing bugs etc.
Their development cycle is backwards.