Grok Bot custom MCP needs static OAuth CLIENT_ID (blocks Oracle NetSuite)

Feature request for product/service

Cloud Agent (GitHub, Slack, Linear,…)

Describe the request

Hey — we hit a hard wall trying to connect Oracle NetSuite to a Grok Bot agent for real accounting work.

We’re trying to use Grok Bot (“Accountant”) to post vendor bills into Oracle NetSuite: match how a supplier was coded last time, create the bill as Pending Approval, attach the PDF, then approve after a human checks it. That’s day-to-day AP work, not a demo.

Oracle NetSuite’s AI Connector (MCP) only works with a pre-registered public OAuth client — fixed CLIENT_ID, authorization-code + PKCE, redirect URL whitelisted on the NetSuite integration record. Dynamic client registration is not accepted.

In Cursor Desktop this is supported via mcp.json:

{
  "mcpServers": {
    "netsuite-name-accountant": {
      "url": "https://<accountId>.suitetalk.api.netsuite.com/services/mcp/v1/all",
      "auth": {
        "CLIENT_ID": "<consumer-key>",
        "scopes": ["mcp"]
      }
    }
  }
}

But in Grok Bot, AddMcpServer only takes name, url, and optional headers. There is no way to attach auth.CLIENT_ID / scopes. So Authorize opens, spins, then Retry — and the agent never gets NetSuite tools.

We already set up a proper NetSuite integration record (Public Client, Authorization Code Grant, NetSuite AI Connector Service scope) with redirect:

That still doesn’t help, because Grok Bot never sends the CLIENT_ID.

Please add the same static OAuth config Desktop has to Grok Bot custom MCP servers (CLIENT_ID, optional secret, scopes), so after auth the tools show up in the Grok Bot agent chat. We need this to actually do accounting work in Oracle NetSuite from Grok Bot — not only from Hermes or Cursor Desktop.

Thanks.

Hey @NoNameNinja!

This should be fixed now. Could you give it another try?

Hey @Colin — just tried again. It works now. NetSuite connected on Grok Bot with the static CLIENT_ID and the tools came through. Thanks for the fix.