Manifest for developers and agents

Manifest is a product development orchestration layer that sits above AI builders. It turns a product description into a phased roadmap with execution-ready build prompts, then keeps that roadmap current as the product ships. This page describes the machine-facing surfaces: the MCP server, the builder integrations, and the state model that agents can rely on.

MCP server: manifest-mcp

Manifest exposes a Model Context Protocol server named manifest-mcp (title "Manifest", version 0.1.0). It lets an MCP-capable client such as Claude, Cursor, or a custom agent read and create Manifest projects on behalf of a signed-in user. Authentication uses OAuth against the Manifest identity provider; every call runs as the authenticated user and is scoped to that user’s workspace.

Access is currently by invitation while the tool contract is versioned and rate limits are put in place. To request access, email hello@trymanifest.dev with the client you intend to connect and what you are building.

list_projects: Returns the signed-in user's roadmap projects with id, name, product type, and target build platform.
get_project_roadmap: Returns the full roadmap for a project: phases, features, subtasks, statuses, and build prompts.
create_project: Creates a new project from an idea. Returns the project id immediately; roadmap generation continues in the background and can be polled with get_project_roadmap.
list_recent_chat_messages: Returns recent messages from a project's planning chat, including AI recommendations and roadmap proposals.

Supported builders

Build prompts are tuned per platform so they can be pasted directly into the tool. Supported today: Lovable, Claude Code, Cursor, Bolt, Replit, and GitHub Codespaces. Each roadmap is generated for one target builder and can be regenerated for another.

The roadmap is a state machine, not a checklist

Feature and subtask statuses in Manifest are never toggled by hand. Every build prompt carries a reporting block; when the prompt is executed in the builder, that block reports back and Manifest advances the matching roadmap items. Amendments to the roadmap (adding, updating, or removing work) flow through reviewed proposals and never change a status. An agent reading a Manifest roadmap can therefore treat status as a record of what actually executed, not what someone intended.

Machine-readable files

Agents and crawlers can start from these files, all served from the site root.

/llms.txt: Short index of the site for language models, following the llms.txt convention.
/llms-full.txt: The full landing and developer copy in one plain-text document.
/sitemap.xml: Sitemap of all public pages.
/robots.txt: Crawl directives, including explicit allowances for AI crawlers.