Your MCP server will drift from your app. Here's a build gate that stops it.

Draft

When I added an MCP server to RyTask (an open-source project tracker), I made one promise: anything a person can do in the UI, an AI agent can do over MCP. No read-only second-class agent access. Full parity.

The problem with promises like that is they rot. You ship a new feature, wire it into the UI and the REST API, and forget the MCP tool. Three sprints later your "100% parity" is 86% parity and you don't know it. So I made parity a thing CI can prove, and fail the build over.

The shape of the system

Every business module in RyTask declares the capabilities it owns and the MCP tools that expose them, in one file: