The MCP server
The front door for agentic callers. Generated from the same OpenAPI spec as your SDK, so the two stay in sync from the first commit.
What agent experience means#
AX is the developer experience an AI agent needs to call your API and get it right. Five things move, and none of them are free.
Tool schemas agents can reason about
Names, descriptions, and parameter schemas an agent can read and act on. A first MCP server often fails here, because the tool descriptions are written for humans skimming docs rather than for a model deciding what to call.
Error semantics that fail safely
An agent does not read errors the way you do. A vague 500 gets retried forever. A 429 with no Retry-After retries at the wrong rate. The error surface needs more care here, not less.
Rate limits for autonomous traffic
Agent traffic is bursty, repetitive, and prone to tight retry loops. You tuned your rate limits and dashboards for human-driven clients, not for this.
Safety guardrails
Some operations have no business running without a human saying yes first. Deciding which tools need approval, and tagging them, is deliberate work, not a checkbox.
Why now#
Across 2025 and 2026 the new integration partners arriving at an API-first SaaS became mostly agents, or tools driven by agents, rather than people writing integration code by hand.
Teams often find this out when a partner asks “do you have an MCP server?” and wants an answer within days. A planned build takes about six weeks. The alternative is a scramble against a partner's deadline.
How we engage#
Four shapes the work tends to take. Each starts with one 30-minute call.
MCP foundation sprint
Fixed-price, 4 to 6 weeks
We ship your first MCP server end to end. Tool schemas designed and reviewed. Error semantics that fail safely. Tested against Claude, ChatGPT, and Cursor before you hand it to a customer.
AX audit
Fixed-price, 2 weeks
You have an MCP server, or you are about to. We test it against the major agentic clients, score it, write up what breaks, and walk you through every finding.
AX retainer
Monthly
For teams whose product roadmap is moving in the agentic direction. Tool schema reviews, customer escalations where an agent failed, roadmap reviews.
Joint DX + AX engagement
Fixed-price or retainer
One spec drives both the SDK and the MCP server. The work overlaps, so we often scope them together.
When this is a fit, and when it is not#
When yes
- A partner has asked about MCP and you are not sure what to ship.
- Your customers are starting to build agentic features, and the agent-readiness questions are landing in your inbox.
- You shipped an MCP server in a hurry and agents stall, fail unpredictably, or call the wrong tool.
- You are early in the API roadmap and want agent-readiness designed in, not bolted on later.
When no
- Your customers are not building agentic features and no partner is asking about MCP. You have time. Watch the space, and come back when your customers get there.
Where the category stands#
AX as a named practice is about two years old. The standards are still settling. MCP is the protocol the industry is converging on, but it is young, and most API-first SaaS still respond to partner requests rather than plan for them.
Teams that get this right in 2026 are likely to be the APIs agents call first for years after. That expectation is the basis of the practice. If your customers or partners are already asking, the work is timely. If they are not yet, it can wait.
Book a 30-minute call#
Thirty minutes to talk through your API and what an MCP server for it would involve.