MCP Standard Tools SuiteApp: Report Tools for AI Clients
The MCP Standard Tools SuiteApp exposes six report-oriented tools (ns_listAllReports, ns_runReport, etc.) that let AI clients retrieve and execute standard and custom NetSuite reports, with notable gaps around accounting periods and custom segment columns.
What changed
The MCP Standard Tools SuiteApp now includes a set of Report Tools that expose NetSuite reporting to external AI clients via MCP. Six tools are available:
ns_listAllReports— returns all standard and custom reports the authenticated user can access.ns_runReport— executes a report by internal ID and returns results. Accepts asubsidiaryIdparameter (positive for individual subsidiaries, negative for consolidated/context subsidiaries).ns_getSubsidiaries— lists subsidiaries with positive IDs (individual) and negative IDs (consolidated/context).ns_getAccountingBooks— lists accounting books for multi-book filtering.ns_getAccountingContexts— lists accounting contexts for report filtering.ns_getNexusIds— lists nexuses for report filtering.
The tools respect the user’s role permissions and support report filters and footer options available in the NetSuite UI. A companion Report Filters MCP App provides an interactive UI for selecting filters.
Consolidated and context subsidiary support
For OneWorld accounts, ns_runReport supports three subsidiary modes via the subsidiaryId parameter:
- Individual — pass the positive internal ID.
- Consolidated — pass the negative internal ID. Returns data for the subsidiary and all its children.
- Context — pass the negative internal ID of a parent/related subsidiary you don’t directly access. Returns data for child subsidiaries you do have access to, converted to the context subsidiary’s currency.
For non-OneWorld accounts, reports use the base currency from Setup > Company > Company Information.
Known limitations
- Accounting periods are not supported. The tools ignore the Report by Period user preference entirely. The AI client cannot see your configured accounting periods and may fall back to calendar-year assumptions or prompt the user for fiscal-year details. This is a significant gap for any account with non-calendar fiscal years or custom periods.
- Custom segment column segmentation — custom reports using custom segments for column segmentation may return
nullvalues. - Custom filters are not supported. Only the standard filter set exposed in the UI is available through MCP.
What to do
- Install or update the MCP Standard Tools SuiteApp if you have not already. The report tools ship as part of this bundle.
- Audit role permissions — the tools inherit the authenticated user’s report access. Verify that the role used by your AI client has the minimum necessary report permissions; do not grant broad analytics access just for MCP convenience.
- Do not rely on period-based reports through MCP yet. If your reporting depends on custom fiscal calendars or accounting periods, continue using the NetSuite UI or SuiteAnalytics Workbook until Oracle adds period support.
- Test custom reports that use custom segments for column breakdowns. If you see
nullvalues in the output, those reports are hitting the known limitation and should be run through the UI instead. - Avoid custom filters in MCP-driven report calls. Only standard filters exposed in the NetSuite report UI are available. If your workflow depends on custom filters, you will need to apply them post-retrieval or use a SuiteQL/saved-search alternative.
- Watch for updates — the accounting-period limitation in particular is likely to be addressed in a future release. Oracle’s documentation does not provide a timeline.
Source: Oracle NetSuite Release Notes