netsuite-mcp-server
Related Servers
Alternatives to netsuite-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI assistants to NetSuite ERP with easy OAuth setup. Provides tools for records, SuiteQL, saved searches, reports, and metadata.15 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes NetSuite REST Record API tools (create, read, update, delete, SuiteQL query, metadata lookup) plus SDF tools for creating custom fields, enabling Claude to manage NetSuite records and configurations.15 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a single MCP endpoint for AI clients to operate NetSuite via a dedicated integration identity, supporting read, write, and action tools with risk policies and audit logging.4,621 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and manage NetSuite data via natural language, supporting SuiteQL queries and record operations through Token-Based Authentication.2MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server providing access to NetSuite data through OAuth 2.0 with PKCE authentication. Works seamlessly with any MCP-compatible client including Claude Code, Cursor IDE, and Gemini CLI.241 npm20MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with the sevDesk accounting API for managing contacts, invoices, credit notes, orders, vouchers, transactions, and parts.3 npm1MIT
TDQS
Scored across 45 tools
Most tools are clearly distinguished by resource type and action, but there is some overlap among vendor retrieval variants (list, latest, by name) and between list vs filtered list for bills. Overall, descriptions help agents select correctly.
All tools use the netsuite_ prefix with snake_case, but collection retrieval inconsistently uses either 'get' or 'list' (e.g., get_vendors vs list_files). One tool also includes 'ns' in its name; otherwise consistent.
With 45 tools, the server carries a large surface. While NetSuite is complex, many similar reference list tools could be consolidated, making this feel heavy and harder to navigate.
Core lifecycle coverage exists for vendors, bills, payments, credits, journal entries, and expense reports. However, there are no delete/void operations and only update support for vendors and bills, which are notable gaps for full record management.