dot•requirements
Server Details
Write product documentation to share with your whole team, including testable specifications.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 20 tools
Most tools target distinct resources or actions, and descriptions clarify pairs like get-document vs show-document. However, create-requirement-document sounds like it creates a document but actually returns formatting guidance, directly overlapping with create-document's space. Several guide-fetching tools (mockup-guide, greenfield-discovery, style-check) also share broad 'get guidance' semantics.
The dominant pattern is consistent kebab-case verb-noun (create-document, edit-mockup, get-requirement, list-projects). Deviations exist: mockup-guide, greenfield-discovery, and style-check are noun phrases, and create-requirement-document uses a create verb for a non-creating guide tool. Overall the convention is still readable and mostly predictable.
20 tools is on the heavy side, but the server covers distinct areas: documents, mockups, requirements, coverage, project listing, and multiple authoring guides. Each tool appears to serve a specific workflow step rather than duplicating another, so the count is reasonable for the domain.
Core document and mockup lifecycles are well covered: create, read, edit, publish, list, show, and search. Requirements are readable and searchable with coverage tools, but delete/archive operations and direct requirement editing are absent, leaving minor gaps agents may need to work around.
Publisher details
- Operator
- Popover AI Ltd · Publisher source
- Operator website
- https://dotrequirements.io
- Vendor relationship
- First-party · Publisher source
- Documentation
- https://docs.dotrequirements.io/tools/ai/mcp
- Privacy policy
- Not provided
- Trust center
- Not available
- Restrictions
- None. Public sign-up. The first OAuth connection creates a free account and workspace. No paid plan, admin approval, or custom OAuth app is needed.
Available Tools
20 toolscreate-documentCreate documentAInspect
Create a new requirements document. PUBLISHES IMMEDIATELY as version 1 — visible to the whole team and to dotreq sync. The markdown's leading H1 is the document's title (omit it for an untitled document). Markdown may embed ```dotrequirements blocks; malformed blocks reject the creation. Returns a shareable link.
Inputs: project (required), markdown (required).
create-mockupCreate mockupAInspect
Create a lofi wireframe mockup — a static sketch of a screen or short flow, attached to a spec so readers see what the words mean. Markup is JSX with every value fixed, written to the mockup dialect: fetch mockup-guide before composing your first mockup. Pass 'document' to attach the mockup to a spec in the same call. A refusal lists every problem with its line — fix them all and retry once.
Inputs: title (required), markup (required), project (required), document.
create-requirement-documentGet the spec style guideARead-onlyInspect
Get the format and this project's conventions for writing a requirements document — the template, the requirement-block syntax, and the label and key patterns this project already uses. Call this BEFORE composing a document with create-document: a document without well-formed dotrequirements blocks publishes as plain prose and contributes no requirements.
Inputs: project (required).
edit-documentEdit documentADestructiveInspect
Edit a document by exact text replacement. old_string must match exactly once against the document as it currently stands (read it first with get-document). The edit lands in the document immediately — anyone with it open sees it — but is NOT published: it reaches repos only when publish-document is called.
Inputs: document (required), new_string (required), old_string (required).
edit-mockupEdit mockupAInspect
Edit a mockup by exact-text replacement: old_string must match the mockup's markup exactly once (use get-mockup to read it). The whole markup re-validates after the edit — an edit that would make it invalid is rejected with the validator's errors and the mockup is unchanged. The result is a lean confirmation, never the full markup. Everyone viewing the mockup sees the change; call show-mockup once after a batch of edits when the user should see the result.
Inputs: mockup (required), new_string (required), old_string (required).
get-documentGet documentARead-onlyInspect
Read a document as it currently stands, as markdown — including work nobody has published yet. This is what edit-document matches old_string against, and what publish-document would carry. The result also says how the document differs from its published version. Find document targets with list-documents.
Inputs: document (required).
get-mockupGet mockupARead-onlyInspect
Read a mockup's title and markup as it currently stands, for your own reasoning and for composing edits. Puts nothing in front of the user — use show-mockup to present it.
Inputs: mockup (required).
get-project-coverage-summaryGet project coverage summaryARead-onlyInspect
Get aggregate test coverage for a project's requirements: which are tested, which aren't, and the coverage percentage. Optionally filter by git branch.
Inputs: project (required), branch.
get-requirementGet requirementARead-onlyInspect
Get a specific requirement by its key (e.g. 'AUTH-1') with all its children (Given/When/Then/And nodes).
Inputs: project (required), requirementKey (required).
get-requirement-coverageGet requirement coverageARead-onlyInspect
Get test coverage for a specific requirement: when it was last tested, on which branch, and in which test file.
Inputs: project (required), requirementKey (required).
greenfield-discoveryGet the greenfield interview protocolARead-onlyInspect
Get the greenfield discovery interview protocol — for working out what a new product or feature should do. Call this when the user is starting something new and has not worked out what it should do, BEFORE drafting requirements from their description. The result is an interview protocol addressed to you; follow it with the user, and write the spec only at its end (create-requirement-document supplies the format and write steps there).
Inputs: no named parameters.
list-documentsList documentsARead-onlyInspect
List a project's documents. Returns each document's title, its target for the other document tools, whether it has ever been published, and whether it currently holds unpublished changes — which may be your own edits, a teammate's, or both.
Inputs: project (required).
list-projectsList projectsARead-onlyInspect
List the dotrequirements projects you can work with. Returns each project's name and the target value the other tools take as their 'project' argument. Call this first when you don't know the project target.
Inputs: no named parameters.
list-requirementsList requirementsARead-onlyInspect
List all requirements in a dotrequirements project. Returns a summary with requirement keys, labels, and content. The caller names the project explicitly — there is no ambient current project.
Inputs: project (required).
mockup-guideGet the mockup authoring guideARead-onlyInspect
Get the guide to authoring a wireframe mockup — the markup dialect, the wireframe component set, what the drawn style discards, and a complete valid example. Call this BEFORE composing your first mockup in a conversation: markup written from general Tailwind and HTML habits is refused, and the guide is what an author needs to write a mockup that is accepted first time.
Inputs: no named parameters.
publish-documentPublish documentADestructiveInspect
Publish a document as it currently stands, sending it to the whole team, to dotreq sync, and to the requirement tools. This carries the WHOLE document, including any unpublished work a teammate has been doing in it — call get-document first and check what it reports as unpublished.
Inputs: document (required).
search-requirementsSearch requirementsBRead-onlyInspect
Search a project's requirements by text or regex. Searches requirement keys, content, and labels.
Inputs: query (required), project (required), useRegex.
show-documentShow documentARead-onlyInspect
Present a document to the user as a styled, read-only document view inline in the chat — requirement cards with keys, criteria, and labels, as it looks in the dotrequirements composer. Use when the user asks to see, review, or discuss a document, and once after completing a batch of edits to one (not after every small edit — each call adds a new view to the conversation). For reading a document's content for your own reasoning, use get-document instead.
Inputs: document (required).
show-mockupShow mockupARead-onlyInspect
Present a mockup to the user, rendered live as a hand-drawn wireframe inline in the chat — they can open depicted menus and move between screens by its links. Use when the user asks to see a mockup, and once after completing a batch of edits (not per edit — each call adds a new view to the conversation). For reading the markup for your own reasoning, use get-mockup instead.
Inputs: mockup (required).
style-checkStyle-check spec contentARead-onlyInspect
Get AI style feedback on requirements content against the project's style rubric. Pass 'markdown' to check content you're composing BEFORE creating/editing a document (recommended), or 'document' to check a document's published content. Provide exactly one of the two.
Inputs: project (required), document, markdown.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Plan products with your team: ideas, specs, screens, decisions, roadmap and issues.
Spec-driven delivery: plans, solutions, ADRs, UX docs, tasks, rules and skills for AI agents.
Your team's PRD, UX spec, architecture and stories: read them, build a story, keep it current.
Structured visual plans and PR recaps with diagrams, prototypes, annotations, and sharing
Related MCP Servers
- AlicenseBqualityDmaintenanceCaptures and organizes requirements as markdown, tracks relationships between personas, requirements, use cases, and user stories.126 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to link spec acceptance criteria to the tests that cover them, list requirements, trace coverage, find gaps, and generate failing test stubs.MIT
- AlicenseNot gradedqualityCmaintenanceEnables generating documentation from source code and templates, building API references from OpenAPI specs, creating architecture diagrams, and searching, versioning, and exporting documents. Supports multiple output formats including Markdown, HTML, PDF, and DOCX.MIT
- FlicenseNot gradedqualityDmaintenanceEnables spec-driven development acceptance gate with structured receipts, audit logs, and reviewer-ready evidence.-
Glama MCP Gateway
Add one secure layer between your agents and this server.