How to
How to connect Claude to NetSuite
NetSuite ships an official Claude connector with a fixed, standard tool set. The catch is that nobody runs a generic NetSuite: your records, custom fields, and saved searches are the parts that make it yours, and the parts a fixed tool set leaves out.
Connect Claude to NetSuite either with the official connector, which ships a fixed, standard set of tools covering a generic slice of the platform, or with a custom MCP connector shaped around how your team actually works. A custom build covers your specific records, custom fields, and saved searches, with posting and deleting gated behind your approval.
Key takeaways
- NetSuite has an official native Claude connector, but it exposes a fixed, generic tool set rather than the records, custom fields, and saved searches your team actually works in.
- A custom connector adds write tools like `create_sales_order`, `draft_invoice`, and `post_journal_entry`, shaped around your account.
- It authenticates through NetSuite with a role you assign, so Claude inherits exactly the permissions that role carries and nothing more.
- Posting, deleting, and other consequential actions are gated write tools that run only after you approve them.
Does NetSuite have an official Claude connector?
Yes. NetSuite ships an official native Claude connector, and it can create and update records. What it exposes is a fixed, standard set of tools covering a generic slice of the platform. Your custom fields, custom records, saved searches, and approval routing are the parts that fixed tool set leaves out.
Start with the honest version: if your team works in vanilla records with standard fields and mostly needs lookups plus routine record changes, connect the official connector and try it first. It may carry the load.
The friction is that almost no company runs a vanilla NetSuite. ERPs get customized because the business demands it: custom fields that drive workflows, custom record types, saved searches the whole team lives in, subsidiaries with their own rules. A generic tool set does not know any of that exists, so Claude ends up working around your configuration instead of inside it.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I set up a custom NetSuite connector for Claude?
A custom NetSuite connector is built for you as a small MCP server that authenticates with OAuth and the narrowest role and permissions the work needs. Read tools and write tools are separated, Claude acts under a role you assign, and posting, deleting, or sending actions wait for your confirmation.
The path from request to working connector:
- 1Describe the NetSuite work Claude should handle, including the record types, custom fields, saved searches, and subsidiaries your team relies on.
- 2We build a small MCP server with read tools (record lookup, saved search) separated from write tools (create, update, post).
- 3You authenticate through NetSuite's OAuth with a role you assign, so Claude inherits exactly the permissions that role carries.
- 4Claude starts creating and updating records in conversation, and posting, deleting, or sending actions run only after you confirm them.
Access is revocable at any time, and if the role cannot touch certain records or subsidiaries, neither can Claude.
What can Claude do in NetSuite with write access?
With full read-write access, Claude creates or updates a sales order from an email or quote you paste in, drafts a customer invoice and routes it for approval, posts a journal entry to the correct accounts and period, and maintains customer, vendor, item, and inventory records.
The tool set maps to the data entry your team still clicks through forms to do:
create_sales_orderto create or update a sales order from an email or quote you paste in.draft_invoiceto draft a customer invoice and route it for your approval.post_journal_entryto post a journal entry to the correct accounts and period.update_recordto create or update customer, vendor, and item records.update_itemto update inventory item details or pricing on a record.
Claude can also look up open transactions matching a saved search and propose batched edits, which is where a connector shaped around your searches pulls ahead of a fixed generic tool set.
Will Claude post transactions or delete records without asking?
No. Posting, deleting, and other consequential actions are separate, gated write tools. Claude can prepare an invoice, journal entry, or record change and show you exactly what will be committed, but it only posts after you approve it. You decide which actions run automatically and which require sign-off.
In practice, most teams let record lookups and saved searches flow freely, keep routine record edits fast, and reserve confirmations for anything that posts to the general ledger, deletes a record, or crosses a subsidiary boundary. The line is yours to draw.
Claude only has the role you assign
The connector authenticates through NetSuite with a role you control, so it inherits exactly the permissions that role carries and nothing more. If the role cannot touch certain records or subsidiaries, neither can Claude, and you can revoke the role at any time.
When is the official NetSuite connector enough, and when is it not?
The official connector is enough when your work stays in standard records with standard fields: generic lookups and routine changes. It stops being enough when the work touches custom fields, custom record types, saved searches, batched edits, or subsidiary-specific rules. Those are custom-connector territory.
A quick self-test: write down the last five things you wished Claude had done in NetSuite. If they are all single changes to vanilla records, connect the official connector today. If any involve a custom field that drives a workflow, a saved search the team runs weekly, or a batch pass over open transactions, a fixed tool set will not carry them, and a connector built around your account will.