Connect by JBRH Open Connect

MCP and a plain API

Use the public API when your software knows what it wants: it has pagination, idempotency, versioning, webhooks and an OpenAPI description you can generate a client from. Use MCP when a *model* has to decide at runtime what to call, because MCP's contribution is discovery and descriptions written to be read by a model rather than by a developer.

Status
Available What this means
Audience
developer
Last verified
Product version
6.3.2

What MCP actually adds#

  • Runtime discovery. A client asks what tools exist and gets typed schemas back, so a model can be told what it may do without anybody hard-coding a list.
  • Descriptions aimed at a model. A tool's description is part of the contract; on a plain API that text lives in documentation the caller may never read.
  • One envelope. Every call has the same shape, so a client can support any server without bespoke code per endpoint.
  • Resources and prompts alongside tools, so context and instructions travel through the same channel as actions.
  • A single endpoint. Streamable HTTP: one URL, POST only in the 2026-07-28 revision.

None of that makes a request faster or more reliable. It makes the surface *legible to something that is deciding as it goes*, which is a real problem and not one REST was built for.

What a plain API does better#

NeedThe API gives youMCP
A generated clientAn OpenAPI 3.1.0 descriptionSchemas per tool, not a client-generation contract
Large result setsPagination, filters, stable orderingThe operations tools pass the API's own limit and cursor through; the other tools return what they return
Safe retriesIdempotency keys and documented semanticsconnect_call_operation accepts idempotency_key; a confirmed operation is performed once
Being told when something happensOutbound webhooks with signature verificationNothing — a tool call is a call
Change managementExplicit versioningA protocol revision, which is a different axis
Multi-step processesArazzo 1.1.0 workflow descriptionsYou orchestrate the calls yourself
Event stream designAn AsyncAPI 3.1.0 descriptionNot applicable

If you are writing a nightly synchronisation, a webhook consumer or a dashboard, the API is the correct answer and MCP would be a detour.

Two doors onto the same operations#

Since October 2026 the MCP operations tools reach every operation of the versioned API — the same handlers, the same checks — as a catalogue a model can search, describe and call. What differs is who decides and who is acting: an API key is a program, while an MCP authorization acts for a person, so consequential operations wait for that person's confirmation and approving held work stays theirs.

Choosing#

  1. Write down who decides which call to make: your code, or a model, at the moment of the request.

    Result Code deciding means the API. A model deciding means MCP.

  2. If it is a model, check whether it needs to be told when something changes.

    Result It probably also needs webhooks, which are an API concern — most real integrations use both surfaces.

  3. Authenticate for the workspace, not for the person.

    Result Both surfaces are workspace-scoped and pass through the allowlist, the workspace kernel and row-level security. Neither is a side door.

Questions#

Is MCP a replacement for the API?

No, and treating it as one produces a client that reimplements pagination and retries badly. They are complementary surfaces over the same workspace-scoped services; most integrations that do anything substantial end up using the API for bulk and events and MCP for the model's own decisions.

Which is more secure?

Neither, because both go through the same three isolation layers and the same authentication requirements. What differs is the failure mode: an MCP server must validate Origin and answer 403 when it is present and invalid, which surprises browser-based clients that work elsewhere.

Can I expose Connect's tools to my own agent?

That is what the MCP server is for, with authentication that resolves to your workspace. Read building an agent on Connect safely first — a tool that can act deserves the same thought as a person who can.