Skip to content

Use Case Fit

As the vast majority of 3Cloud use of the technology will be to build Corporate-level applications , this article focuses on some Enterprise needs.

Better with OAuth 2.1...

The recent addition of the OAuth 2.1 protocol will speed the adoption of the "remote" MCP server which is what most Enterprise use cases require to secure access to the corporate tools.

However, many Enterprise application patterns have not yet been established.

What about Agent-to-Agent Communication?

Many Enterprise use cases require to use a multi agent architecture and the protocol for agent-to-agent communication does not have (yet) a winner.

  • It is not yet clear whether the MCP protocol needs to be used in combination of other protocols (such as A2A) for complex multi agents Enterprise systems.
  • The MCP protocol is stateful which makes the concept of sampling (terribly named) possible whereby the MCP server can request the client (today via a SSE session) to ask its associated LLM completion of a request (See Sampling - Model Context Protocol),
  • Anthropic/AWS which is the main backer of the MCP protocol may add the ability for agents to communicate by:
  • adding better support for async communication - See YouTube,
  • OAuth Dynamic Client Registration (See RFC 7591) could be very useful for a multi-tenant SaaS client agent but major Identity Providers do not support this RFC.

What about resource sharing?

The MCP protocol does not provide a mechanism to share resources and an MCP "resource" does not have the concept of state to know if a resource is available (e.g. uploading a blob in Azure Blob Storage)

What about scalability concerns?

The stateful nature of the MCP protocol does not allow for serverless deployment and therefore would not necessarily work well for Enterprise scale demands.

  • The protocol needs to be stateful to offer this agent-to-agent communication (see above), - See Transports - Model Context Protocol
  • An effort to use an Streamable HTTP transport rather than SSE where HTTP can be the transport after a feature negotiation phase between the client and the server is considered:

  • See RFC - Replace HTTP+SSE with new "Streamable HTTP" transport by jspahrsummers · Pull Request #206 · modelcontextprotocol/modelcontextprotocol

  • The MCP protocol did not support asynchronous communication (as is the case for Google A2A) in its first version, but support has been added for long running tasks with the ability to call back for task status. See MCP Async Processing: Guide to Model Context Protocol. However, when watching this presentation from AWS back in June 2025, it implies that the async support is not yet finalized and the following patterns could be added to the protocol:

  • Event driven where the client provides a webhook for the server to respond to,

  • Callback mechanisms for the client to check for completion status