"Error fetching connectors" & 500 Error from /list-accessible after adding custom MCP connector

I built a test MCP server and was testing out ChatGPT’s custom connectors. When I tried adding the connector yesterday (prior to agent launch) I received an error saying my server didn’t meet the specifications. Digging deeper, found that it was because it didn’t have a “search” tool.

Tried to add it again today after the launch of ChatGPT Agent, just to see if they had improved it to allow for any kinds of tools. I didn’t get the same error, but the tool wasn’t added. Now when I refresh the page, I can’t view any of my connections (I had added gmail and google drive). I am receiving this 500 error:

Endpoint: /backend-api/aip/connectors/list_accessible
Payload: {type: “USER”, id: “user-knqdNhcsmKqAUjH76WaubTZd”}
Response: {“detail”:{“message”:“None is not a valid ConnectorSafetyStatus”}}

Looks like the connector got added but is malformed, causing the list endpoint to break. Any help/assistance on either removing the faulty connector or resetting my list of connectors would be much appreciated!

2 Likes

I have exactly the same issue

the same from my side. After last release the process seems broken or we need to put something extra. However no available documentation how we can resolve this

Looks like OpenAI has resolved this issue. I can now view my connectors again, and my custom connector shows up under the “Browse connectors” section. If I try to add it, it once again says “This MCP server doesn’t implement our specification: search action not found” as expected. Thanks all for giving this some visibility!