Context
• Goal: Expose a Custom Tool to an external AI client (Claude) via NetSuite MCP.
• Project type: ACP (not SuiteApp).
• Account: tstdrvXXXXXX (SB).
• Client URLs tried:
– https://tstdrvXXXXXX.suitetalk.api.netsuite.com/services/mcp/v1/all
– https://tstdrvXXXXXX.app.netsuite.com/services/mcp/v1/all
What I built
• Script: vendormanagement_acp.js — SuiteScript 2.1 with u/NScriptType CustomTool.
• Schema: vendormanagement_schema_acp.json — method names match the JS exports.
• Tool XML: customtool_vendormanagement_acp.xml — correct scriptfile/rpcschema paths to /SuiteScripts, exposeto3rdpartyagents=T.
What I already tried
- Added u/NScriptType CustomTool; redeployed.
- Verified schema vs JS names; validated JSON (also tried adding "nullable": []).
- Confirmed XML paths point to the correct files.
- Removed the entire <permissions> block (also tried VIEW/EDIT variants earlier).
- Reconnected Claude multiple times to both URLs above (using the suitetalk.api host primarily).
- Used a non-Admin role with: – MCP Server Connection – Log in using OAuth 2.0 Access Tokens (Also tested with Admin.)
- exposeto3rdpartyagents=T in XML.
- Reconnected after each deploy; also removed/re-added the connector in the AI client.
- Removed any questionable permkeys from earlier versions (e.g., LIST_FIND).
- Aware that record.load.promise could be risky; listing shouldn’t depend on it, but noted.
Result
• The tool still does not appear in the Claude AI Connector TOOL list when connecting to /v1/all (both hosts tested).
- Has anyone recently listed ACP Custom Tools under /services/mcp/v1/all in SB? Any hidden feature flag required beyond the two permissions above?
- When <permissions> is removed from the tool XML, does the OAuth role still need specific Lists/Transactions perms to make the tool visible?
- Any known ACP vs SuiteApp enumeration differences (e.g., SuiteApp-only reliability)?
- If a module throws during load, does MCP silently skip the tool? Any way to capture those errors server-side?
- A known-good minimal “ping/echo” sample that always enumerates in SB to compare against?
PS: I tried to eploy a tiny “ping/echo” smoke-test Custom Tool (no permissions) to confirm account/connector vs code - still didn't appear on the list.