MCP and A2A do different jobs, so most teams need MCP first and A2A only later, if at all. The Model Context Protocol (MCP) connects one AI agent to tools and data, such as NetSuite records, saved searches or an integration flow. The Agent2Agent protocol (A2A) connects one agent to another agent, so it can hand off a task and get the result back. For NetSuite today, the ERP side speaks MCP: Oracle's NetSuite AI Connector Service is an MCP server, and Celigo and n8n both expose integrations as MCP tools. We found no A2A support documented by Oracle, Celigo or n8n as of November 17, 2026. If your agent needs to read or write NetSuite, you need MCP or an API. A2A comes in only when that agent must delegate work to an agent another team or vendor runs, and that agent then uses MCP to reach the ERP.

At a glance

  • MCP: agent to tools and resources. The A2A project's own guide calls it "vertical": each MCP connection gives one agent another tool.
  • A2A: agent to agent. "Horizontal": your agent discovers another agent, sends it a task and follows that task until it finishes. Specification version 1.0.0.
  • Not rivals: the A2A specification calls them complementary. An agent that receives an A2A task may use MCP to do the work.
  • NetSuite, Celigo, n8n: MCP is documented for all three. A2A is not documented for any of them; n8n has third-party community nodes only.
  • Where A2A already works: Microsoft Copilot Studio can call external agents over A2A and tools over MCP, and Microsoft's docs recommend MCP servers for tools and A2A for agents.

MCP vs A2A: the comparison in one table

The A2A specification ends with a short appendix on MCP, and the A2A project publishes a longer comparison guide. Both describe MCP as the standard for how an agent "connects to and interacts with tools, APIs, data sources, and other external resources", and A2A as the standard for how "independent, often opaque, AI agents communicate and collaborate with each other as peers." The table puts the practical differences side by side.

MCP (Model Context Protocol)A2A (Agent2Agent)
ConnectsAn agent to tools, APIs and data sourcesAn agent to other agents
The other side isA tool with defined inputs and outputs, often stateless: a database query, a record lookupAn agent that reasons, plans, uses its own tools and keeps state over a longer exchange
Unit of workA tool call that returns a structured resultA task with an ID and a lifecycle: submitted, working, input required, auth required, completed, failed, canceled, rejected
How it is foundThe client lists the tools an MCP server offersAn Agent Card (JSON) describes the agent's skills, endpoint and auth; the specification's well-known location is /.well-known/agent-card.json
VisibilityThe agent sees and chooses each tool"Opaque execution": agents don't share internal state, memory or tools
Long-running workDepends on the toolBuilt in: streaming over Server-Sent Events, and push notifications to a webhook you provide
AuthSet by each MCP server (NetSuite: OAuth 2.0 sign-in under a NetSuite role)Declared in the Agent Card: API key, HTTP auth, OAuth 2.0, OpenID Connect or mutual TLS
Who maintains itBoth are projects of the Agentic AI Foundation (AAIF), which the Linux Foundation directs. A2A, announced by Google in April 2025, joined as a Growth Stage project on August 27, 2026, with MCP listed as a sibling project.

A2A 1.0 defines three ways to carry the protocol: JSON-RPC 2.0 over HTTP, gRPC, and HTTP+JSON (REST). That matters less to an ERP team than the task lifecycle. Two of those states, input required and auth required, let a remote agent pause and ask for something, which is how a human approval or a fresh sign-in fits into an agent-to-agent hand-off.

What NetSuite, Celigo, n8n and Copilot Studio support today

This is where most MCP vs A2A explainers stop being useful for an ERP team. They compare the protocols in the abstract. What you can actually build depends on what your ERP and integration platform implement, and today that is MCP.

PlatformMCPA2A
Oracle NetSuiteYes. The NetSuite AI Connector Service is NetSuite's MCP endpoint; the MCP Standard Tools SuiteApp supplies the tools, and you can build custom ones. Administrator roles and roles with full permissions can't use it.Not documented. Oracle's AI Connector Service pages describe MCP only.
CeligoYes, two ways: the Celigo MCP Server exposes tools you define across connected systems, and the hosted Platform MCP lets an agent operate your integrator.io account.Not documented as a product feature. Celigo's July 2026 blog post on A2A vs MCP positions its integration layer as the governed access underneath agents, whichever coordination protocol they use.
n8nYes. The MCP Server Trigger node makes workflows available to MCP clients; the MCP Client node calls other MCP servers. Both are core nodes.No core node. Community nodes add A2A (third-party, not maintained by n8n); n8n's June 2026 blog post points to them for teams experimenting.
Microsoft Copilot StudioYes, through MCP servers.Yes. Add agent → A2A agent, with no auth, an API key or OAuth 2.0. It runs on the custom connector infrastructure, so it can reach A2A agents on-premises or in a virtual network.

Microsoft's page includes the clearest vendor guidance we found. Its "when to use" table sends APIs and basic HTTP services to custom connectors, "MCP tools or resources" to MCP servers, and agents that already implement A2A to an A2A connection, and it notes you can combine them in one agent.

One detail to check if you connect the two: Microsoft's page tells you to look for the Agent Card at the agent's endpoint plus /.well-known/agent.json, while the A2A 1.0 specification uses /.well-known/agent-card.json. If Copilot Studio doesn't fill in your agent's name and description, check which path your agent serves.

How MCP and A2A fit together around NetSuite

The A2A specification's own description of the combination is: a client agent asks a server agent to perform a task, and the server agent "might use MCP to interact with several underlying tools, APIs, or data sources" to complete it. Here is what that looks like with an ERP in the middle. This is our illustration, not a vendor reference design:

  1. A sales team's agent in Copilot Studio needs to know whether a customer can take a large order on credit. It doesn't hold NetSuite access, and it shouldn't.
  2. It sends an A2A task to a credit-check agent that the finance team runs. It found that agent through its Agent Card and authenticated with the scheme the card declares.
  3. The finance agent uses MCP to read the customer's balance, open invoices and credit limit: through the NetSuite AI Connector Service, a narrow tool in a Celigo MCP Server, or an n8n workflow behind the MCP Server Trigger.
  4. If a person must approve, the task moves to input required and waits instead of failing.
  5. The finance agent returns the answer as the task's result. The sales agent never sees NetSuite, the finance agent's tools or its credentials.

The ERP connection is MCP in every version of this. A2A only decides who is allowed to ask the agent that holds it.

When you need A2A, and when MCP is enough

Use these criteria rather than adopting both protocols because both are in the news:

Where the controls belong

A2A's opaque execution is a feature for collaboration and a constraint for governance. The calling agent can't inspect the remote agent's tools, so it can't enforce what those tools do to NetSuite. The controls have to sit with the agent, and the MCP server, that touches the ERP:

Microsoft's A2A page makes the same point from the other side: when you connect agents outside Copilot Studio, you're responsible for their use, including data handling, permissions, approvals and traceability.

Where we would start

This is our recommendation, not a vendor's:

  1. Get the MCP layer right first. Pick how agents reach NetSuite (native AI Connector, Celigo MCP Server or n8n workflows), scope a dedicated role, and start read-only. Everything in A2A sits on top of this.
  2. Add writes as narrow, approved tools with validation and an audit trail, before any second agent can trigger them.
  3. Add A2A when a real hand-off appears: another team's agent, a partner's agent, or a Copilot Studio agent that needs an answer from your finance agent. Publish an Agent Card that declares the auth scheme, and keep NetSuite credentials on your side of the hand-off.

For where agents sit relative to the ERP more broadly, see System of Record vs System of Action. On the n8n side, n8n's MCP Server Trigger for NetSuite shows the workflow-as-tool pattern.

Frequently Asked Questions

What is the difference between MCP and A2A? MCP connects an AI agent to tools, APIs and data sources, such as NetSuite records or an integration flow. A2A connects an agent to other agents, so it can discover them, send them a task and follow that task to completion. MCP gives one agent more capabilities; A2A lets separate agents work together.

Is A2A replacing MCP? No. The A2A specification describes the two as complementary, and both are projects of the Linux Foundation-directed Agentic AI Foundation. An agent that receives an A2A task often uses MCP to do the work.

Does NetSuite support A2A? Not as of November 17, 2026. Oracle documents the NetSuite AI Connector Service as an MCP server with the MCP Standard Tools SuiteApp and custom tools. We found no A2A support in Oracle's documentation.

Do Celigo or n8n support A2A? Neither documents native A2A support as of November 17, 2026. Both support MCP: Celigo through its MCP Server and Platform MCP, n8n through the MCP Server Trigger and MCP Client nodes. For n8n, third-party community nodes add A2A.

Do I need A2A to connect an AI agent to NetSuite? No. Connecting an agent to NetSuite is an MCP (or API) job. You need A2A only when that agent must delegate work to, or take work from, another agent that runs separately, such as a Copilot Studio agent owned by another team.

Which AI platforms support both MCP and A2A? Microsoft Copilot Studio documents both: MCP servers for tools and resources, and A2A connections to external agents, which you can combine in one agent. The A2A project lists SDKs for Python, Go, Java, JavaScript, .NET and Rust for building your own A2A agents.

Entech Solutions is a Celigo integration partner and builds n8n workflows. We connect AI agents to NetSuite, Salesforce and the systems around them through governed MCP tools. See our AI Agents & MCP page, or talk to us about which layer your agent project needs first.

Sources, checked November 17, 2026: A2A Protocol Specification 1.0.0 (including Appendix B, Relationship to MCP); A2A and MCP: Detailed Comparison; A2A joins the Agentic AI Foundation (August 27, 2026); Google: Announcing the Agent2Agent Protocol (April 9, 2025); Microsoft Learn: Connect to an agent over the A2A protocol; Oracle: NetSuite AI Connector Service; n8n: MCP Server Trigger; n8n blog: Agent-to-agent protocol; Celigo blog: A2A vs MCP. Celigo MCP Server and Platform MCP details are from Celigo's documentation as cited in our linked Celigo articles. Vendors add protocol support quickly, so check these pages for anything newer.