I added the Netsuite AI Connector to my ChatGPT Pl...
# ai-netsuite
p
I added the Netsuite AI Connector to my ChatGPT Plus account but am getting this message when saving the connector: This MCP server can't be used by ChatGPT to search information because it doesn't implement our specification: search action not found Any ideas on this?
m
As per specs ChatGPT expects output in a slightly different format. The tools are still usable without any issues. Just make sure that if you are using your custom-deployed tool, it should have a nullable property in the schema for any output key that can be empty. All of this is documented in the NetSuite Custom Tools Schema guide.
👍 1
b
@pen one you need to be using developer mode in either a chatgpt pro or plus plan
m
In the pro/plus plan with dev mode enabled, it allows you to add untrusted MCP sources. But still the warning will popup as it expects search/fetch tools at the moment.
👍 1
s
Do you have a pro or business account? I found that pro can use the connector with the mcp in Dev (you are) and chat gpt should be in dev mode too. If you are using a business account (like i do) You cannot use the standard tool and need to create your own tool (stupid AF) Make sure you have the correct tools. If you have ChatGPT Business: Build your tools. ChatGPT Business supports only fetch and search tools, that are not included in the MCP Standard Tools SuiteApp, and you must build them yourself. For more information, see Creating Custom Tools for the NetSuite AI Connector Service. If you have ChatGPT Plus or Pro, you can use the MCP Standard tools SuiteApp, but you must first enable the Developer mode in ChatGPT. Before enabling Developer mode, review the Associated Risks, Controls, and Mitigation Strategies topic, as well as any OpenAI documentation about risks and safety of the MCP and the Developer mode. If you're confident to proceed, go to Setting > Connectors > Advanced > Developer mode.
p
We actually have the Team version.
y
@pen one the team account actually does not support the developer mode right now. That is why this error is being thrown