This article is relevant if you already know the basics of the NetSuite AI Connector Service, but your ChatGPT connection still refuses to come together cleanly.
TL;DR Summary
I spent about 1.5 hours going back and forth on this before I finally saw the issue clearly. The setup is confusing because ChatGPT reveals the needed Callback URL in one registration mode, but NetSuite 2026.1 expects the connector to be completed under another. If you already have the foundational NetSuite setup in place, the fix is straightforward once you know where to look.
Background
For most of 2026, I had been using the Claude.ai connection with NetSuite’s AI Connector Service. When I came back to OpenAI ChatGPT in June 2026, my old ChatGPT connection was no longer working. My first suspicion was simple authentication expiration; that was not the whole story, but it pointed me in the right direction.
As I worked the problem, I found a short NetSuite notice tied to March 4, 2026, that specifically called out ChatGPT. That was the clue that explained why this issue felt different from the earlier connection experience.
This article builds on Chidi Okwudire’s excellent foundation piece, How to Connect NetSuite to ChatGPT and Claude Using the New AI Connector. His article is the right source for the one-time account features, role design, governance, and the broader MCP framework. I do not want to duplicate that work here. I want to isolate the one setup wrinkle that can still catch a prepared administrator off guard.
NetSuite Administrators should Focus on the Missing Clue
If you have already followed the broader setup guidance, the remaining issue is usually not the global configuration. It is the registration sequence.
Chidi already covers the foundational requirements: enable the correct NetSuite features, use a custom non-admin role, include MCP Server Connection, Log in using OAuth 2.0 Access Tokens including REST Web Services, and keep the role narrow. If any of that is not in place, stop and use his article first.
Note, click images to see them full screen.
The Puzzle in Plain English
One value moves between the two systems, but each side labels it differently. Plus, you must toggle the client twice, which is counterintuitive.
- Naming Conventions: ChatGPT refers to it as the Callback URL. NetSuite calls it the Redirect URI. Same value.
- Client Registration Option: The confusing part is that ChatGPT only shows that value when you temporarily choose User-Defined OAuth Client. But when you complete the NetSuite 2026.1 connection, ChatGPT needs to be switched back to Dynamic Client Registration (DCR).
That is the fix.
The Short Path that Worked for Me
Assuming the NetSuite account, features, and role are already correctly configured, here is the sequence that mattered:
- In ChatGPT, create the app and enter the NetSuite MCP server URL. See endpoint options below.
- Set authentication to OAuth.
- In Advanced OAuth settings, temporarily switch to User-Defined OAuth Client so ChatGPT reveals the Callback URL.
- Copy that value.
- In NetSuite, create the integration record so the Redirect URI exactly matches that Callback URL, with Dynamic Client Registration enabled.
- Go back to ChatGPT and switch the registration method back to Dynamic Client Registration before clicking Create. This is the step that produced my blindness.
- Complete consent with the dedicated non-admin role.
Quick Reference: Choose the Endpoint
Use this endpoint for the full toolset:
https://<accountID>.suitetalk.api.netsuite.com/services/mcp/v1/all
Use this endpoint for the standard tools only:
https://<accountID>.suitetalk.api.netsuite.com/services/mcp/v1/suiteapp/com.netsuite.mcpstandardtools
Where Administrators Tend to Stumble
The most common mistake is understandable. Once ChatGPT finally reveals the Callback URL, it is easy to assume you should just keep going from there. But leaving ChatGPT in User-Defined OAuth Client mode at the final create step leads you into the wrong path.
The more accurate mental model is this: use that mode only to harvest the value NetSuite needs; then return ChatGPT to DCR so the registration completes the way NetSuite 2026.1 expects.
If it Still Fails
- Invalid Login Attempt usually means ChatGPT was still left in User-Defined OAuth Client mode when the connection was created.
- invalid_redirect_uri usually means the Redirect URI on the NetSuite integration record does not exactly match the Callback URL that ChatGPT presented.
Both failures point back to the same lesson: the basic account setup may be fine; the issue is often the registration sequence and exact URI match.
A Practical Note from the Field
This is one of those problems where nothing is conceptually beyond a NetSuite administrator, yet the experience still feels oddly slippery. That was certainly true for me. I knew enough to keep working the problem; I still spent about 1.5 hours bouncing between screens before the pattern became obvious.
That is exactly why I wanted to get this written down. Administrators who land here have probably already done the foundational work. What they need is the missing clue, not a long reintroduction.
This guidance reflects what I observed with ChatGPT and NetSuite 2026.1 in June 2026. For the broader account setup, role design, and governance model, start with Chidi Okwudire’s article: How to Connect NetSuite to ChatGPT and Claude Using the New AI Connector.
If you found this article relevant, feel free to sign up for notifications to new articles as I post them. If you are trying to make AI connections to NetSuite reliable and supportable, let’s have a conversation.
