Skip to main content
    Industry Insights

    The MCP Tools SuiteApp Lets NetSuite CRM Compete

    With Claude as the interface, managing your pipeline in NetSuite just makes sense.

    Brian Wenzl
    Brian Wenzl
    The Glue Guy

    NetSuite's MCP tools are rightly getting a lot of attention. But every blog post I've seen about the NetSuite AI Connector Service is pitched at CFOs. Ask NetSuite about Q2 churn. Find AP anomalies. Pull a report without waiting on the analyst. It’s all good stuff, and it’s sold a lot of tokens already.

    Based on what we’re seeing at Opal Creek, it may matter at least as much for CRM.

    NetSuite CRM has Often Been an Afterthought or an Also-Ran

    NetSuite CRM is perfectly capable. It tracks leads and opportunities, forecasts, and connects to the same customer record that drives quotes, orders, invoices, projects, and AR.

    But reps complain about it. It feels dated. The mobile app is [redacted]. By contrast, Salesforce feels modern. Reps spend all day in the CRM, and they want it to feel good. For fifteen years, Salesforce has been the obvious choice. Reasonably so. It’s a great product and it gets better every year.

    Plenty of NetSuite shops bought Salesforce anyway for that reason. Then they built an integration so finance could see what sales was doing. Two platforms, two contracts, ongoing middleware, reconciliation work, separate admin skill sets. For a lot of organizations that's the right decision, but it comes at a cost.

    What Changes When the Interaction Layer Moves

    We installed NetSuite's MCP tools into our own production account and started reviewing our pipeline through Claude alongside the NetSuite UI.

    What does our pipeline look like this quarter? Which opportunities haven't moved in 30 days? Chart closed-won deals by source over the last year. Who haven't we talked to in a while? Give me a brief on this account before my call tomorrow.

    The answers came back fast and clean. Most of those questions were already answerable with a saved search or a workbook, but this was faster and I found myself asking questions I wouldn't have bothered with before.

    One System, No Limits

    Here is what a sales rep can ask the LLM when the data lives in NetSuite.

    I've got a call with Beacon Health at 2. What do I need to know?

    The answer will include open opportunities, recent interactions, open and recently closed support cases, AR aging, the last three invoices and whether they paid on time, active projects and status, contract renewal date, and who the rep's last two conversations were with.

    You can get to the same brief in Salesforce with a solid ERP integration. The integration just has to exist, stay current, and have the right fields mapped. If you’re already running NetSuite for the back office, that data is sitting right there without any of that plumbing.

    After the call, a rep updates the CRM:

    Just wrapped with Beacon. Dana's in. She needs to loop in their CFO, wants to close end of May, bumped to $240k. Next step is a security review by their IT team; I'm sending materials tomorrow.

    A couple of short sentences, spoken into the Claude app on their phone the moment the call ends. That’s all the MCP connector needs to log an activity, update a close date and opportunity amount, create a follow-up task, and add a note on the Customer record.

    You Probably Don’t Need to Write Anything

    The out-of-the-box MCP Standard Tools are quite capable. You get SuiteQL query execution, saved search access, and record create/update through REST Web Services. Between those three primitives and a model that's good at translating intent into queries, most rep workflow is there today. Pipeline queries, account briefs, activity logging, opportunity updates, forecast rollups.

    If you want to go further, you can. With the 2026.1 release, NetSuite upgraded its handling of custom tools written in SuiteScript 2.1. They added better tool management and proper execution logging. Oracle has a sample project on GitHub with some custom tools so you can see how they’re constructed.

    The places we’re considering writing custom tools are where the standard tools technically work but a purpose-built version would be tighter. A log_sales_interaction tool that takes a meeting summary and does the full multi-record fanout in one shot. An account_360_brief tool that assembles the cross-lifecycle pre-call view in a single call. A forecast_commit_builder that walks a rep through their pipeline and writes structured commit data.

    You can do all of these with the standard kit. A custom tool makes the shape consistent, governs permissions your way, and avoids asking the model to stitch three queries together every time.

    What This Means for the CRM Decision

    For organizations running NetSuite and deciding what to do about CRM for the first time, the MCP Tools SuiteApp makes NetSuite a strong candidate: put the upstream and downstream data in the same system. If you're already running Salesforce today with a working integration and a trained sales team, the evaluation is much more complex and will be dominated by considerations of change management and data migration.

    If you're somewhere in between, with an SFDC/NetSuite integration that's been a headache or a Salesforce renewal you're not excited about, it's worth thinking it through carefully.

    Caveats

    NetSuite CRM plus MCP is not feature-equivalent to Salesforce. Salesforce has a deeper Configure-Price-Quote story, more mature marketing automation, and an ecosystem of sales tools that assume Salesforce as the hub.

    High-velocity BDR operations are not well-served by this architecture today. If your reps are logging hundreds or thousands of calls per day, doing it in Claude or ChatGPT probably isn’t better. Most of our clients are operating at a more modest scale of CRM activity.

    Finally, all of this is new. The custom tool script type shipped recently and 2026.1 added logging and observability, but it’s still early.

    Where We Are at Opal Creek

    We're going to keep using the MCP tools in our own account, share it with clients who fit the profile, and experiment with building some custom tools as reference implementations. We'd love to show you what we're working on.

    Further Reading: