DEV Community

Cover image for MCP vs A2A for NetSuite and ERP AI Agents
Andrey Tverdomed for Entech Solutions

Posted on Originally published at integrationstars.com

MCP vs A2A for NetSuite and ERP AI Agents

Originally published on integrationstars.com. Facts checked against the A2A specification, Microsoft, Oracle, n8n and Celigo documentation on November 17, 2026.

Short answer: MCP and A2A do different jobs. The Model Context Protocol connects one AI agent to tools and data. The Agent2Agent protocol (A2A) connects one agent to another agent so it can hand off a task and get the result back. If your agent has to read or write NetSuite, that is an MCP (or API) job. A2A comes in only when the agent must delegate work to an agent another team or vendor runs.

The difference in one table

MCP A2A
Connects An agent to tools, APIs and data An agent to other agents
Unit of work A tool call with a structured result A task with a lifecycle (working, input required, auth required, completed, failed, canceled, rejected)
Discovery The client lists a server's tools An Agent Card at /.well-known/agent-card.json (spec 1.0)
Visibility The agent sees each tool "Opaque execution": no shared state, memory or tools
Auth Set by each MCP server Declared in the Agent Card: API key, HTTP, OAuth 2.0, OpenID Connect, mTLS

The A2A specification calls the two complementary: an agent that receives an A2A task may use MCP to do the work. Both are now projects of the Linux Foundation-directed Agentic AI Foundation.

What ERP-side platforms support (as of Nov 17, 2026)

  • Oracle NetSuite: MCP through the NetSuite AI Connector Service and the MCP Standard Tools SuiteApp. No A2A documented.
  • Celigo: MCP through the Celigo MCP Server and the hosted Platform MCP. No A2A documented as a product feature.
  • n8n: MCP Server Trigger and MCP Client are core nodes. A2A only through third-party community nodes.
  • Microsoft Copilot Studio: both. Its docs send "MCP tools or resources" to MCP servers and agents that implement A2A to an A2A connection.

One gotcha: Microsoft's page looks for the Agent Card at /.well-known/agent.json, while A2A 1.0 uses /.well-known/agent-card.json. If Copilot Studio doesn't pick up your agent's name, check which path you serve.

When you need A2A

  • MCP alone is enough when one agent (or several in one app) calls tools one team controls.
  • Consider A2A when the other side is an agent owned by another team or company, or the work is long-running and needs follow-up questions or approvals.
  • Don't use A2A to avoid governing ERP access: the controls (scoped NetSuite role, narrow write tools, logging) stay with the agent that holds the MCP connection.

The full article has the vendor-support table with details, a worked NetSuite credit-check example and a three-step rollout: MCP vs A2A for NetSuite and ERP AI Agents.

Sources: A2A specification, A2A and MCP guide, Microsoft Learn: A2A in Copilot Studio, Oracle: NetSuite AI Connector Service, n8n: MCP Server Trigger.

Top comments (0)