Specifai MCP Server

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.

[!WARNING] This server is currently experimental. The functionality and available tools are subject to change and expansion as we continue to develop and improve the server.

Table of Contents

• Requirements
• Installation
• Configuration
• Preparing Your Project
• IDE Integration
• Available Tools
• Contributing
• Security
• License

Requirements

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

Installation

# Latest version
npx --yes @presidio-dev/specifai-mcp-server@latest

# Specific version
npx --yes @presidio-dev/[email protected]

We recommend npx to install the server, but you can use any node package manager of your preference such as yarn, pnpm, bun, etc.

Configuration

with npx with latest version:

{
  "specifai": {
    "command": "npx",
    "args": ["--yes", "@presidio-dev/specifai-mcp-server@latest"],
    "disabled": false,
    "autoApprove": []
  }
}

with npx with specific version:

{
  "specifai": {
    "command": "npx",
    "args": ["--yes", "@presidio-dev/[email protected]"],
    "disabled": false,
    "autoApprove": []
  }
}

Preparing your project

This is completely optional, but it's recommended to use it to avoid having to specify the project directory path every time you access the server. For AI IDE / Extension (Hai Build), it's recommended to use a .specifai-path file to specify the project directory path.

Make sure your project root directory contains a .specifai-path file. It's how the Specifai MCP server knows where to find the specification documents generated by Specifai.

The file is a plain text file containing the absolute path to the project directory where the specification documents for a project are stored.

For example, if your project directory is located at /path/to/project, the .specifai-path file should contain the following line:

/path/to/project

Specifai MCP integration with popular IDE and extension

See the setup instructions for each

Add the following to your hai_mcp_settings.json file. To open this file from Hai Build, click the "MCP Servers" icon, select the "Installed" tab, and then click "Configure MCP Servers".

See the Hai Build MCP documentation for more info.

{
  "mcpServers": {
    "specifai": {
      "command": "npx",
      "args": ["-y", "@presidio-dev/specifai-mcp-server@latest"]
    }
  }
}

Add the following to your Amazon Q Developer configuration file. See MCP configuration for Q Developer in the IDE for more details.

The configuration file can be stored globally at ~/.aws/amazonq/mcp.json to be available across all your projects, or locally within your project at .amazonq/mcp.json.

{
  "mcpServers": {
    "specifai": {
      "command": "npx",
      "args": ["-y", "@presidio-dev/specifai-mcp-server@latest"]
    }
  }
}

First, enable MCP support in VS Code by opening Settings (Ctrl+,), searching for mcp.enabled, and checking the box.

Then, add the following configuration to your user or workspace settings.json file. See the VS Code MCP documentation for more info.

"mcp": {
  "servers": {
    "specifai": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@presidio-dev/specifai-mcp-server@latest"]
    }
  }
}

The easiest way to install is with the one-click installation button below.

Alternatively, you can manually configure the server by adding the following to your mcp.json file. This file can be located globally at ~/.cursor/mcp.json or within a specific project at .cursor/mcp.json. See the Cursor MCP documentation for more information.

{
  "mcpServers": {
    "specifai": {
      "command": "npx",
      "args": ["--yes", "@presidio-dev/specifai-mcp-server@latest"]
    }
  }
}

Add the following to your ~/.codeium/windsurf/mcp_config.json file. See the Windsurf MCP documentation for more information.

{
  "mcpServers": {
    "specifai": {
      "command": "npx",
      "args": ["-y", "@presidio-dev/specifai-mcp-server@latest"]
    }
  }
}

You can add the Specifai MCP server in Zed by editing your settings.json file (accessible via the zed: settings action) or by using the Agent Panel's configuration UI (agent: open configuration). See the Zed MCP documentation for more information.

Add the following to your settings.json:

{
  "context_servers": {
    "specifai": {
      "command": {
        "path": "npx",
        "args": ["-y", "@presidio-dev/specifai-mcp-server@latest"]
      }
    }
  }
}

Available Tools

The server provides several tools for interacting with your specification documents:

| Tool Name | Description | | ------------------ | ---------------------------------------- | | 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 | | search | Full text search across all documents |

Contributing

We welcome contributions to the Specifai MCP Server! Please see our Contributing Guide for more information on how to get started.

Development Setup

For detailed instructions on setting up your development environment, please refer to our Development Setup Guide.

Architecture

To understand the project architecture, please see our Architecture Guide.

Security

For information about our security policy and how to report security vulnerabilities, please see our Security Policy.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgements

• Model Context Protocol - The protocol specification this server implements
• Specifai - The project this server integrates with