// MATE
Symfony Mate
Give coding agents reliable access to your running app, and the know how to use it.
A running thread through my work: a coding agent can read your code but cannot look into the running application, so it guesses. Mate is the tool that gives it the right tools instead. These pieces are the thinking around it, from what it should expose, to how you distribute know how to agents, to why the transport was never the point.
article
Giving AI assistants eyes →
What Mate is: tools that let a coding agent look into a running Symfony app, not just read its code.
article
Skills over MCP: shipping Symfony know-how with Mate →
Serving know how to agents over the same connection as the tools.
article
The last mile: distributing Agent Skills to real agents →
No agent reads Skills over MCP yet. Getting them onto the filesystem agents actually watch.
article
The wrong debate: what PHP taught me about agentic software →
MCP or CLI is the wrong fight. What PHP already learned about building things together, one layer down.
article
Kill the MCP →
I deleted the MCP server from my own MCP project and kept the tools. Kill the reflex, not the protocol.