Local MCP (Retired)

Earlier versions of dot•requirements shipped a local MCP (Model Context Protocol) server that AI coding assistants connected to. It’s retired. Its jobs are now served by two better-fitting surfaces:

Coding assistants use the CLI directly. Every MCP tool has a CLI verb equivalent, and the workflow guidance dotreq ai-setup installs tells your agent which verbs to run and when — no server to configure, no restart, no per-assistant MCP setup. See Agent Workflow.
Chat apps use the MCP server. Claude and other chat assistants connect to your dot•requirements workspace over the hosted MCP server with your own account.

Migrating

Run setup again:


dotreq ai-setup

It removes the old MCP registration from your assistant’s configuration and installs the current workflow guidance. That’s the whole migration.

If an assistant still tries to launch the old server (npx @popoverai/dotrequirements mcp), it exits with a message pointing here.

Tool → Verb Mapping

If you had habits built on the MCP tool names:

Retired MCP tool	CLI verb
`search_requirements`	`dotreq search`
`get_requirement`	`dotreq get`
`list_requirements`	`dotreq list [--untested]`
`get_requirements_by_test`	`dotreq requirements-for`
`get_tests_by_requirement`	`dotreq tests-for`
`create_requirement_document`	`dotreq create-requirement-document`
`validate_requirements`	`dotreq validate`
`style_check`	`dotreq style-check`
`review_test`	`dotreq review-test`
`report_coverage`	`dotreq report`
`push_requirements`	`dotreq sync`

For CI/CD, the MCP server’s --auth-from-env flag is gone: the CLI now authenticates from DOTREQ_PROJECT_ID / DOTREQ_PROJECT_SECRET automatically when no settings file is present. See CI/CD Integration.