# MCP Server

The boot-free MCP server behind agent workflows: what each of the ten registry-backed tools does and when an agent reaches for it, and how it fits with llms.txt and the installable skills.

Poetry's agent surface is a standard stdio MCP server, `bundle exec poetry-agent`: boot-free (it reads the committed registry, never boots Rails) and read-only by design. Its ten tools close a verify loop: `compose` routes any brief to a vetted block or the matching components, `build_page` runs a five-step guided workflow for whole screens, `list_components`/`describe_component` disclose contracts at `brief|detailed|full` depth, and `check` returns a line-numbered PASS/FAIL verdict - the same linter as `bin/rails poetry:check`. `list_blocks`/`describe_block` serve the composed-screen catalog with full ERB source, `list_recipes` surfaces the multi-file payloads, and `get_skill`/`guidance` serve the installed skill text at runtime. The same registry projects `/poetry/llms.txt` and `/poetry/llms-full.txt`, so no surface can drift. The server also answers POST JSON-RPC over HTTP (`mount Poetry::Agent::MCP::HTTP.new => "/mcp"` - this site serves it at /mcp), the same surface for in-page bridges. Editor configuration lives on the Editors page.