MCP

The problem it solves

Model Context Protocol: a contract for exposing tools and resources to a model inside a session.

Technical rationale

MCP interests me as a boundary rather than an integration: the model asks for a schemed tool and receives what that tool returns, instead of receiving a context dump and inferring the rest. In Pokédex Manager I wrote the server so the internal assistant and an external client cross the same read-only surface, because a second route to the data is a second chance to forget per-account isolation.

How I have used it

I wrote the MCP server in Pokédex Manager: six read-only tools that the assistant and external clients consume through the same boundary, so the assistant cites what a tool returned.