Plan transaction replication
Prepare a sync for supported transaction objects, keeping transaction headers and their nested line items together.
Your connection path
Your assistant works through your Stacksync workspace and its available connections.
“Plan order reporting with line items”
Stacksync MCP · ERP
Use Stacksync MCP to plan NetSuite customer and transaction syncs, inspect available workflow actions and investigate integration failures. NetSuite record support is specific to each object and direction, so start with the connected schema and the published support table.
01 / The connection
Use Stacksync MCP to plan NetSuite customer and transaction syncs, inspect available workflow actions and investigate integration failures. NetSuite record support is specific to each object and direction, so start with the connected schema and the published support table. Choose an AI client below to get started with the Stacksync MCP server.
The server belongs to Stacksync. The available NetSuite operations depend on your connection, permissions, and connector modules.
Explore the NetSuite connector →02 / Capabilities
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Prepare a sync for supported transaction objects, keeping transaction headers and their nested line items together.
Discover the modules and connection available for a NetSuite task before choosing an action or filling its form.
Read sync issues and current mappings to separate access problems, record validation and mapping errors.
03 / Setup
Connect the MCP server first. Then connect NetSuite using the requirements below.
Connect Claude on the web or desktop to Stacksync through a custom connector and browser sign-in.
Open Customize → Connectors, select + Add, then Add custom connector. Name it Stacksync and use the server URL below.
https://mcp.stacksync.com/mcp Select Connect, complete the Stacksync sign-in in your browser and choose the default workspace. Clear Make changes on the consent screen if you only want read access.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available NetSuite connection and capabilities.
Add the remote Stacksync server to Claude Code and authenticate from its MCP menu.
Run the command below. Add --scope user if you want the connection available across your projects.
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp Open Claude Code, run /mcp, select stacksync and complete the Stacksync sign-in. Choose the workspace you want requests to use by default.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available NetSuite connection and capabilities.
Add Stacksync as a custom MCP app in ChatGPT and sign in with OAuth.
Open Settings → Apps → Advanced settings and turn on Developer mode. If the option is unavailable, check the account or workspace policy with your administrator.
Select Create app, name it Stacksync, enter the server URL below and choose OAuth. Complete the Stacksync sign-in and select your default workspace.
https://mcp.stacksync.com/mcp Select Stacksync from the chat tools menu so the conversation can use its tools. Signing in to ChatGPT itself does not sign you in to Stacksync.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available NetSuite connection and capabilities.
Configure Stacksync in Codex with a remote MCP URL and an explicit OAuth login.
Add the Stacksync endpoint to your Codex MCP configuration.
codex mcp add stacksync --url https://mcp.stacksync.com/mcp Run the login command and complete the Stacksync browser sign-in. Select a default workspace; restart your Codex session if the tools are not yet listed.
codex mcp login stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available NetSuite connection and capabilities.
Use Stacksync from Cursor by adding a remote server to its MCP configuration.
Merge this stacksync entry into the mcpServers object in ~/.cursor/mcp.json. Preserve any servers you already use.
{
"mcpServers": {
"stacksync": {
"url": "https://mcp.stacksync.com/mcp"
}
}
} Open Cursor’s MCP settings, select Connect beside stacksync and finish the Stacksync sign-in in your browser.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available NetSuite connection and capabilities.
Connect Stacksync to GitHub Copilot Chat in VS Code using an HTTP MCP server.
Run the command below. Alternatively, add a stacksync entry with type http and this URL under servers in your project’s .vscode/mcp.json.
code --add-mcp '{"name":"stacksync","type":"http","url":"https://mcp.stacksync.com/mcp"}' Open Copilot Chat in Agent mode. Start stacksync from the tools picker and complete the Stacksync browser sign-in.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available NetSuite connection and capabilities.
Add Stacksync to Cascade with Windsurf’s serverUrl configuration and OAuth sign-in.
In the Cascade panel, open the … menu and select Open MCP config file. Merge this entry into mcp_config.json without removing other servers.
{
"mcpServers": {
"stacksync": {
"serverUrl": "https://mcp.stacksync.com/mcp"
}
}
} Save the configuration. Cascade opens the Stacksync sign-in flow the first time it uses the server. Choose your default workspace.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available NetSuite connection and capabilities.
Connect the Gemini command-line client to Stacksync through remote HTTP MCP and browser authorization.
Run the following command in your terminal to add the HTTP server.
gemini mcp add --transport http stacksync https://mcp.stacksync.com/mcp Start Gemini CLI, run the command below and finish the Stacksync sign-in in your browser.
/mcp auth stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available NetSuite connection and capabilities.
04 / Put it to work
Example prompts for NetSuite. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
Inspect my NetSuite and PostgreSQL connections, available transaction fields and existing syncs. Propose a one-way sales-order reporting sync that preserves the parent transaction ID and nested itemList data. Show how reporting can expand lines without treating them as independently writable NetSuite rows. Do not save or start the sync until I review the plan.
A transaction-aware reporting design that preserves NetSuite’s parent and line-item structure.
Inspect the NetSuite connector modules and connection. Determine whether the customer lookup and update needed for my request are available, then read their forms. Propose the exact record identifier and changed fields using only values I supply or authorize you to inspect. If an action is missing, explain the gap. Do not execute a write.
A customer update proposal grounded in the actual module and required inputs.
Inspect my NetSuite connection and the saved searches it exposes. Review existing syncs, then propose a one-way export of the saved search I select into a reporting destination. Mark the source as read-only and list the fields and refresh expectations to validate. Ask for approval before creating or changing resources.
A read-only saved-search export plan with explicit field and refresh validation.
05 / Before you run
OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.
Read about permissions and approvals ↗06 / Common questions
No. The support table distinguishes read and write by object. Saved Searches are read-only, and some objects or writes require access to be requested.
No. The documented sync model stores lines within the parent transaction. You can expand that data for reporting, but changes intended for NetSuite must return through the parent transaction and its complete line-item value.
No. NetSuite and NetSuite SuiteAnalytics Connect are separate connectors. Do not infer NetSuite write support from a SuiteAnalytics reporting connection.
Reviewed · Product documentation and connector references
Keep building