The conversation about agentic AI has moved on from should we use it to how will it actually reach our software? In the last six months, two of the most influential labs in the field have committed to opposing answers, and the divergence is no longer academic.

Anthropic’s bet is the Model Context Protocol, or MCP. Every application worth talking to publishes a structured server. The agent connects to that server, sees the tools and data the application has explicitly exposed, and operates within those boundaries. Clean, fast, audit-ready. The premise is that the software industry will build these servers fast enough to matter.

OpenAI’s bet is computer use. The agent drives the same graphical interface a human drives. It opens applications, clicks buttons, types into fields, reads what’s on the screen. No structured integration required. The premise, in their own framing, is that your apps don’t need an API anymore.

These are not subtle differences in implementation. They are different theories about the future of business software.

The MCP bet is conditional on enterprise software vendors moving fast. If they do, Claude-style agents inherit a clean, structured lane to every system that matters. Trust accounting platforms publish a trust-accounting MCP server with explicit authority boundaries. Compliance registries publish a registry MCP server. Supplier portals publish a procurement MCP server. The agent never has to guess what anything means; the protocol tells it.

The computer-use bet is conditional on something more pessimistic. The bet is that enterprise vendors won’t move fast enough, especially in long-tail categories like government registries, regional suppliers, and three-decade-old council compliance portals. If most of the software an agent needs to touch will never expose an integration, the only path that scales is to teach the agent to use the screens themselves.

In April 2026, OpenAI shipped a major Codex update with more than 90 new plugins. Buried in the announcement was a detail that changed the strategic picture: those plugins are bundles of skills, app integrations, and MCP servers.

OpenAI didn’t abandon computer use. It added MCP as a parallel pathway. Codex, Claude Code, Cursor, Microsoft’s Agent Framework, and Gemini CLI have all converged on MCP as the standard contract for structured tool access, while keeping computer-use capabilities for the long tail.

The lesson is not that one bet won. The lesson is that the smart architecture supports both.

Strata managers might be tempted to read this as a debate that doesn’t reach them. It does, and faster than most operators expect.

In our April Insight From Chatbot to Colleague, we pointed to the Macquarie data showing 24% of Australian strata businesses already deploying autonomous agents. Less discussed: every committee, owner, and supplier interacting with a strata firm is increasingly bringing their own AI agents to the relationship. An owner asking Claude or ChatGPT to “lodge a maintenance request for unit 408,” “summarise the last three years of levies for my apartment,” or “find out when the next AGM is and add it to my calendar” is no longer a hypothetical interaction. It is a routine one.

When that owner-side agent reaches your platform, it has two options:

• The clean lane: a structured server (MCP) that explicitly tells the agent what it’s allowed to do, with authority boundaries, audit trails, and deterministic responses.
• The fragile lane: scraping public web pages, screenshotting, guessing field names, and submitting forms with no audit context.

Every platform without a structured agent surface will be operated through the fragile lane by default, because owners and committees will not wait for vendor roadmaps to catch up with what their AI tools already do today.

StrataPort has made the deliberate bet to do both, and to do them in a specific order.

The three tracks are not redundant. They serve different time horizons and different agent populations. Track 1 is the cleanest path for first-party agentic workflows the firm operates inside StrataPort. Track 2 is the substrate for the broader integration ecosystem we wrote about in The Integration Imperative. Track 3 is the graceful-degradation path for everything else.

It is tempting to read “build both” as expensive optionality. We read it as the lower-risk position.

• Picking only MCP assumes vendor-side adoption catches up before owner-side agents become commonplace. In the long tail of regulators, councils, and regional suppliers, it will not.
• Picking only computer use assumes the protocol layer never matures into the standard. It already has. Every major lab now ships MCP support.
• Picking neither assumes the agentic shift will pause to wait. It will not.

The firms whose technology partners are hedged across both pathways inherit two things: a clean, audit-ready surface for the agents that arrive structured, and graceful degradation for the agents that don’t. That is the same logic that runs through everything we’ve written about agentic operations. The platform’s job is to enforce the boundaries between deterministic and probabilistic, structured and unstructured, governed and ungoverned. Connectivity is not a feature. It is a survival posture.

One thing the dual-track architecture does not change: the deterministic guardrails we wrote about in Deterministic vs Probabilistic. Trust account reconciliation, levy calculation, capital works fund movements, and AGM voting tabulation remain firmly inside the rules-based engine, whether the request arrives via MCP, REST, computer use, or a logged-in human at a keyboard. The protocol only ever determines how the request was made. It does not determine what the system is allowed to do in response. That distinction is non-negotiable.

An MCP server is not a relaxation of governance. It is a more rigorous enforcement of it. Authority boundaries become explicit, audit trails become structured, and the agent’s scope is documented in the protocol itself rather than implied by the UI it happened to land on.

The agent access question is not MCP or computer use. It is do you have a deliberate posture, or are you about to be operated through whatever pathway happens to win the next news cycle?

StrataPort’s posture is straightforward: build the structured lane first, document the public lane next, stay compatible with the long-tail lane always. That is the position we believe will look obvious in 2027, and prudent in 2026.