Specifai MCP Server

If you already use Specifai, the specifai mcp server is the piece that lets your assistant work with it directly. Specifai MCP Server that runs over stdio.

What the server does

A Model Context Protocol (MCP) server for Specifai project integration and automation with any MCP-compatible AI tool. This server is designed to be tool-agnostic, meaning it can be used with any tool that supports the MCP protocol. This server currently exposes tools to read all documents generated by the Specifai project.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• get-brds — Get Business Requirement Documents
• get-prds — Get Product Requirement Documents
• get-nfrs — Get Non-Functional Requirements
• get-uirs — Get User Interface Requirements
• get-bpds — Get Business Process Documents
• get-tcs — Get Test Case Documents
• get-user-stories — Get User Stories for a specific PRD
• get-tasks — Get Tasks for a specific User Story
• get-task — Get details of a specific Task
• set-project-path — Set or change the project directory path
• get-task-by-id — Get details of a specific Task by ID
• list-all-tasks — List all available tasks

Credentials and setup notes

• Node.js >= 16.0.0 - Bun >= 1.0.0 (if using Bun runtime) - Hai Build, Cursor, Windsurf, Claude Desktop or any MCP Client

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Specifai's toolset — get-brds, get-prds, get-nfrs and 11 more — is a fair guide to whether it matches your workflow. It is maintained by presidio-oss; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Specifai's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Specifai.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.