NetSuite MCP — "Couldn't reach the MCP server" post-OAuth, empty MCP execution log

[ERPBEANZ]

MCP server URL or name

NetSuite

How are you connecting to this server?

From browsing the MCP server directory

Where does the issue occur?

When auth finishes and redirects back to Claude.ai

When did you last reproduce this?

2026-05-05

Browser and OS

Chrome 147.0.7727.138 (arm64) MacOS Tahoe 26.4.1

Describe the issue

Connecting NetSuite (native connector) via claude.ai web fails post-OAuth with "Couldn't reach the MCP server" despite OAuth completing successfully on the NetSuite side. NetSuite's MCP execution log shows zero requests from Claude's broker, indicating the broker authenticates and then fails before making any MCP call.

Error details

- **ofid:** `ofid_aaf50426bca824ae`
- **Date of failure:** 2026-05-05
- **Client:** claude.ai web (incognito, no extensions)
- **Connector:** NetSuite (native)

error shown: Couldn't reach the MCP server. You can check the server URL and verify
the server is running. If this persists, share this reference with
support: "ofid_aaf50426bca824ae"

Expected behavior

After successful OAuth, Claude's broker should make MCP requests against the authenticated endpoint, populating the AI Connector Service execution log and making MCP tools available in conversations.

Additional context

Further evidence of issue:

NetSuite-side logs show OAuth succeeds but no MCP request is ever made:

1. NetSuite Login Audit Trail: Confirms successful authentication during Connect attempts. OAuth completes and tokens are issued.

2. Claude AI integration record → AI Connector Service (MCP) execution log: Completely empty. Zero MCP requests received from Claude's broker, despite OAuth completing successfully.

Environment context

• Production NetSuite environment has never connected successfully — every attempt fails post-OAuth with the symptoms above.
• The same NetSuite account's sandbox environment has connected successfully in the past using the same SuiteApp, same role pattern, same OAuth flow. Prior to authenticating in NetSuite production we are selecting the production environment and then the configured role.

NetSuite-side configuration (validated as non-cause)

• Claude AI integration record: Present, State = Enabled (also tested Block → unblock cycle); execution log empty confirms broker never attempts MCP calls.
• MCP role permissions: MCP Server Connection, OAuth 2.0 Authorized Applications Management, Log in using OAuth 2.0 Access Tokens — all present.
• MCP Standard Tools SuiteApp: Installed and active in production.
• OAuth handshake: Succeeds (confirmed via NetSuite Login Audit Trail).

Reproduction steps

1. Install MCP Standard Tools SuiteApp in NetSuite production
2. Configure MCP role with required permissions
3. claude.ai → Settings → Connectors → NetSuite → Connect
4. Complete OAuth flow (succeeds — confirmed in NetSuite Login Audit Trail)
5. Observe "Couldn't reach the MCP server" error in claude.ai
6. Check NetSuite integration record's AI Connector Service (MCP) execution log → empty

[localden]

Thank you for the report and for confirming your NetSuite MCP execution log was empty. That was the key signal.

What's happening: After OAuth completes, Claude sends an authenticated MCP initialize request to your NetSuite account. NetSuite responds with HTTP 200, an empty body, and no Content-Type header instead of a JSON-RPC response. The request reaches NetSuite's infrastructure, but the MCP component doesn't process it, which matches your observation that the MCP execution log is empty.

Claude treats a 200 with no JSON-RPC body as an unusable response and reports "Couldn't reach the MCP server." That message is misleading here, since the server was reached but returned nothing useful. We're looking at improving the error copy.

The most likely cause is missing configuration in your NetSuite account. Things to check:

1. In NetSuite, confirm the NetSuite MCP SuiteApp (com.netsuite.mcpstandardtools) is installed and enabled for your account.
2. Confirm the MCP feature is enabled under your account's feature settings.
3. Confirm the integration role you authenticated with has the necessary permissions to access the MCP server.
4. If you're connecting to a sandbox or test-drive account, confirm the SuiteApp is installed there specifically. Installation doesn't carry over between environments.

If you've confirmed those and still hit the error, retry the connection and share a fresh flow_id from the error URL so we can investigate further.