How does the agent reach the backend I already run?
Tools and MCP
Tool calling, the Model Context Protocol, per-tenant connections, and how to expose an API you did not design for a model.
5 posts
Start here
Connect an AI agent to the backend you already run
You do not need a new API surface for an agent. You need to describe the one you have, and decide what it is never allowed to touch.
- The architecture of an in-app agent, for people who approve itEvery box in the system, who owns it, where the trust boundaries sit, and what changed between the intent-classification era and the one where a model chooses.Tools and MCP9 min
- Designing a tool surface an agent can actually useTwo independent vendors put the practical ceiling near twenty tools. Everything else about tool design follows from the model reading your schema and nothing else.Tools and MCP9 min
- MCP for in-app agents: connecting your tools to a modelThe Model Context Protocol replaces one connector per backend with one protocol. What it is, how a tool call actually happens, and what it costs on the first turn.Tools and MCP10 min
- Where the seconds go in an in-app agent turnWe measured a slow turn end to end. Most of the time was not in our code and not in the model, which changes what is worth optimising.Tools and MCP10 min