Your AI agent can read every file in your repository. It knows your schema, your route handlers, the half-finished migration you left in alembic/versions. Ask it how to build almost anything and it will tell you.
Ask it what to build and it has nothing.
That asymmetry bothered me for months. I'd be in Claude Code planning a sprint, and the actual demand signal , what users were asking for, how many wanted it, and crucially why was sitting in a browser tab the agent couldn't see. So I'd alt-tab, skim the board, mentally rank things, come back, and re-type the conclusion as a prompt. Every single time.
I run a feedback board product, so the fix was obvious in retrospect: expose the board over MCP. This post is about the design decisions that turned out to matter, because most of them weren't obvious going in.
Why MCP instead of just a REST API
