get-bpds
Get Business Process Documents for this project
LABSCO SUMMARY
The requirements stop living in a separate tool and start arriving in the agent's context, scoped to what you asked for.
Descriptions are omitted by default and the listings are paged, which is what keeps a full PRD set from swallowing the context window — pull the detail only for the document you land on. Drop a .specifai-path file in the project root and the path questions stop; without one, every call has to carry a cwd.
What it is
A read-only server over a Specifai project's generated specification documents, exposing them as tools any MCP client can call. Paged, with descriptions left out unless you ask for them.
What you get
- Each document family on its own tool: business requirements, product requirements, non-functional requirements, user interface requirements, business process documents and test cases — returned as ID and title, with the description off by default
- The PRD hierarchy walked in order: user stories under a PRD, tasks under a user story, and a single task in full
- list-all-tasks for a flat inventory across every PRD and user story at once, and get-task-by-id when you already know the ID
- search over all documents by text content or by PMO ID, with the document type returned alongside the match
- Linkage IDs carried through wherever they exist: Azure DevOps and Jira IDs and issue types, plus PMO IDs
- set-project-path to point the server at a different project when it cannot infer one
Requirements
Node.js >= 16.0.0, or Bun >= 1.0.0 on the Bun runtime, and a project whose specification documents were generated by Specifai. Run it over stdio with npx --yes @presidio-dev/specifai-mcp-server@latest. Every tool takes a cwd and the server tries to infer the project directory from the environment; put a .specifai-path file containing the absolute path in your project root so you never have to pass it, or call set-project-path once. The author marks the server experimental — the tool surface is expected to change.
Setup effort
One command — npx -y @presidio-dev/specifai-mcp-server@latest
USE CASES
01
Finding the requirement behind the ticket you were handed
Search every document type at once by text or PMO ID, and see which type the match came from.
02
Working from a product requirement down to a single task
List the PRDs, open the user stories under one, then the tasks under a story.
03
Reading one task in full when you already have its ID
Fetch the complete task object without paging through everything else.
04
Checking what non-functional constraints apply before you design
Pull the NFRs with their descriptions included.
05
Taking stock of everything outstanding
List every task across all PRDs and stories as a flat inventory, IDs and titles only.
06
Pointing the server at a different project
Set the path explicitly when the environment gives it nothing to infer from.
13 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-brds
Get Business Requirement Documents for this project, returns ID, Title, Description(not included by default)
get-nfrs
Get Non-Functional Requirement Documents for this project, returns ID, Title, Description(not included by default)
get-prds
Get Product Requirement Documents for this project, returns ID, Title, Description(not included by default), Ado Id (When PRD/US/Task is linked to ADO), Jira Id (When PRD/US/Task is linked to JIRA), PMO Id(when available), Ado Issue Type(when available), Jira Issue Type(when available), and LinkedBRDIds (when available)
get-task
Get list of Tasks for a particular User Story in a particular PRD
get-task-by-id
Retrieves complete information about a specific task when you know its exact ID. This tool provides direct access to a single task's details without having to retrieve and filter through all tasks., returns full task object, ID, Title, Description, Ado Id (When Task is linked to ADO), Jira Id (When Task is linked to JIRA), PMO Id(when available), Ado Issue Type(when available), Jira Issue Type(when available)
get-tasks
Get Tasks for a particular User Story
get-tcs
Get Test Case Documents for this project
get-uirs
Get User Interface Requirement Documents for this project
get-user-stories
Get User Stories for a particular PRD
list-all-tasks
List all the tasks available across all PRDs and User Stories, without task description, only return ID, Title, Ado Id (When Task is linked to ADO), Jira Id (When Task is linked to JIRA), PMO Id(when available), Ado Issue Type(when available), Jira Issue Type(when available)
search
Search documents by text content or Pmo ID across all documents, returns document ID, Title, Description, Type, Ado Id (When PRD/US/Task is linked to ADO), Jira Id (When PRD/US/Task is linked to JIRA), PMO Id(when available), Ado Issue Type(when available), Jira Issue Type(when available)
set-project-path
Update the project path and reload the solution. use this tool only when we not automatically able to infer the project path or asked by the user or us., we will try to auto infer it from the environment first.
BEFORE YOU INSTALL
What to know first
Tools you get
13 tools when we connected. The tools read documents generated by Specifai; set-project-path points the server at a different folder and writes nothing.
Requires
- Node.js >= 16.0.0
- Bun >= 1.0.0 (if using Bun runtime)
- Hai Build, Cursor, Windsurf, Claude Desktop or any MCP Client
- Make sure your project root directory contains a .specifai-path file
Where it runs
All 6 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 13 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @presidio-dev/specifai-mcp-server@latestMCP Clients
Hai Build, Amazon Q, Windsurf
JSON
{
"mcpServers": {
"specifai": {
"command": "npx",
"args": [
"-y",
"@presidio-dev/specifai-mcp-server@latest"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"specifai": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@presidio-dev/specifai-mcp-server@latest"
]
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"specifai": {
"command": "npx",
"args": [
"--yes",
"@presidio-dev/specifai-mcp-server@latest"
]
}
}
}Zed
ZED · JSON
{
"context_servers": {
"specifai": {
"command": {
"path": "npx",
"args": [
"-y",
"@presidio-dev/specifai-mcp-server@latest"
]
}
}
}
}
