Really like the line “your codebase is your context.”
One place I’d extend this: AI-readable code helps the agent understand the repo, but agents also need readable execution environments.
That’s where MCP gets interesting. A clean codebase tells the agent what the app is trying to do. An MCP server can tell it what the outside system actually does: available tools, expected inputs, state transitions, webhook outcomes, logs, and failed runs.
For API integrations, this is a big shift. Instead of an agent only reading code + docs and guessing, it can use MCP to run the workflow before editing the code.
So the stack becomes:
code clarity → repo context
MCP → execution context
agent → better changes
We’re exploring this with FetchSandbox MCP for API workflows: giving agents a stateful sandbox they can execute against before touching app code.