MCP server intelligence profile

Specifai MCP Server

A Model Context Protocol (MCP) server for Specifai project integration and automation with any MCP-compatible AI tool. This server currently exposes tools to read all documents generated by the Specifai project

Local OnlyOfficial distributionpresidio-oss
Verified cleanNpm · 0.5.1

Our scanner tested version 0.5.1 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.

1Distribution channel
13Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

Install @presidio-dev/specifai-mcp-server from npm

Version 0.5.1 declares 1 executable entrypoint.

npm install --save-exact @presidio-dev/specifai-mcp-server@0.5.1
npx -y -p @presidio-dev/specifai-mcp-server@0.5.1 @presidio-dev/specifai-mcp-server
MCP client configuration example
{
  "mcpServers": {
    "@presidio-dev/specifai-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@presidio-dev/specifai-mcp-server@0.5.1",
        "@presidio-dev/specifai-mcp-server"
      ]
    }
  }
}

Identity

Canonical slugspecifai-mcp-server-0cde0801DeploymentLocal Only
Canonical packagenpm:@presidio-dev/specifai-mcp-serverRepositorypresidio-oss/specifai-mcp-server
First published—Latest release—
Last security verification—Classification confidence90%
PublicationPublishedOfficial distributionYes

Distributions

ChannelIdentifierCurrent versionVersionsSource
npm@presidio-dev/specifai-mcp-server0.5.11Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npm@presidio-dev/specifai-mcp-server0.5.1CurrentSep 5, 202613 toolsSucceeded · 0 resources · 0 promptsFailed
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

Provenanceartifact_hash_verifiedSignature—
MCP SDK@modelcontextprotocol/sdk Artifact SHA-25657a200c70e225f35a9c4fb7107ce7e45ae1bc12eda56eb2ea9353f5f9a785525
Scannermcp-proof-engine 0.1.0Scan completedAug 20, 2026
Security rating39 / 100Methodologyversion-rating-1.0
Executable entrypoints
[
  "@presidio-dev/specifai-mcp-server"
]
Rating reasons
[
  "security_contact_or_disclosure"
]

Current protocol inventory

2024-11-05Negotiated protocol
specifaiServer-reported name
1Capability groups
Aug 17, 2026Observed

Tools 13

ToolCategoryAnnotationsRisk
get-bpdsGet Business Process Documents for this project
Input schema
{
  "type": "object",
  "properties": {
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    }
  },
  "includeDescription": {
    "type": "boolean",
    "description": "Include description in the output, default is false"
  },
  "limit": {
    "type": "number",
    "description": "Limit the number of documents to return, default 10"
  },
  "offset": {
    "type": "number",
    "description": "Offset the number of documents to return, default is 0"
  },
  "required": [
    "cwd"
  ]
}
——
get-brdsGet Business Requirement Documents for this project, returns ID, Title, Description(not included by default)
Input schema
{
  "type": "object",
  "properties": {
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    },
    "includeDescription": {
      "type": "boolean",
      "description": "Include description in the output, default is false"
    },
    "limit": {
      "type": "number",
      "description": "Limit the number of documents to return, default is 10"
    },
    "offset": {
      "type": "number",
      "description": "Offset the number of documents to return, default is 0"
    }
  },
  "required": [
    "cwd"
  ]
}
——
get-nfrsGet Non-Functional Requirement Documents for this project, returns ID, Title, Description(not included by default)
Input schema
{
  "type": "object",
  "properties": {
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    },
    "includeDescription": {
      "type": "boolean",
      "description": "Include description in the output, default is false"
    },
    "limit": {
      "type": "number",
      "description": "Limit the number of documents to return, default is 10"
    },
    "offset": {
      "type": "number",
      "description": "Offset the number of documents to return, default is 0"
    }
  },
  "required": [
    "cwd"
  ]
}
——
get-prdsGet 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)
Input schema
{
  "type": "object",
  "properties": {
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    },
    "includeDescription": {
      "type": "boolean",
      "description": "Include description in the output, default is false"
    },
    "limit": {
      "type": "number",
      "description": "Limit the number of documents to return, default is 10"
    },
    "offset": {
      "type": "number",
      "description": "Offset the number of documents to return, default is 0"
    },
    "includeUserStories": {
      "type": "boolean",
      "description": "Include user stories in the output each user stories will include ID and Title, Description will not be included, default is false"
    },
    "includeTasks": {
      "type": "boolean",
      "description": "Include tasks in the output each task will include ID and Title, Description will not be included, default is false"
    }
  },
  "required": [
    "cwd"
  ]
}
——
get-taskGet list of Tasks for a particular User Story in a particular PRD
Input schema
{
  "type": "object",
  "required": [
    "prdId",
    "userStoryId",
    "taskId",
    "cwd"
  ],
  "properties": {
    "prdId": {
      "type": "string",
      "description": "The ID of the PRD to get user stories for, PRD ID convention is PRD<PRD Number>, PRD number is zero padded with minimum 2 digits, e.g. PRD01, PRD12, PRD103, etc."
    },
    "userStoryId": {
      "type": "string",
      "description": "The ID of the User Story to get tasks for, US ID convention is US<US Number>, US number is non zero padded, e.g. US1, US12, US103, etc."
    },
    "taskId": {
      "type": "string",
      "description": "The ID of the Task to get, TASK ID convention is TASK<TASK Number>, TASK number is non zero padded, e.g. TASK1, TASK12, TASK103, etc."
    },
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    }
  }
}
——
get-task-by-idRetrieves 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)
Input schema
{
  "type": "object",
  "required": [
    "taskId",
    "cwd"
  ],
  "properties": {
    "taskId": {
      "type": "string",
      "description": "The unique identifier for the task you want to retrieve Must follow the format: TASK followed by a number without leading zeros Examples: TASK1 TASK12, TASK103 Note: The number portion is NOT zero-padded (use TASK1, not TASK01), Convert the Task ID to mentioned format to use this tool."
    },
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    }
  }
}
——
get-tasksGet Tasks for a particular User Story
Input schema
{
  "type": "object",
  "required": [
    "prdId",
    "userStoryId",
    "cwd"
  ],
  "properties": {
    "prdId": {
      "type": "string",
      "description": "The ID of the PRD to get user stories for, PRD ID convention is PRD<PRD Number>, PRD number is zero padded with minimum 2 digits, e.g. PRD01, PRD12, PRD103, etc."
    },
    "userStoryId": {
      "type": "string",
      "description": "The ID of the User Story to get tasks for, US ID convention is US<US Number>, US number is non zero padded, e.g. US1, US12, US103, etc."
    },
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    }
  }
}
——
get-tcsGet Test Case Documents for this project
Input schema
{
  "type": "object",
  "properties": {
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    },
    "includeDescription": {
      "type": "boolean",
      "description": "Include description in the output, default is false"
    },
    "limit": {
      "type": "number",
      "description": "Limit the number of documents to return, default is 10"
    },
    "offset": {
      "type": "number",
      "description": "Offset the number of documents to return, default is 0"
    }
  },
  "required": [
    "cwd"
  ]
}
——
get-uirsGet User Interface Requirement Documents for this project
Input schema
{
  "type": "object",
  "properties": {
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    },
    "includeDescription": {
      "type": "boolean",
      "description": "Include description in the output, default is false"
    },
    "limit": {
      "type": "number",
      "description": "Limit the number of documents to return, default is 10"
    },
    "offset": {
      "type": "number",
      "description": "Offset the number of documents to return, default is 0"
    }
  },
  "required": [
    "cwd"
  ]
}
——
get-user-storiesGet User Stories for a particular PRD
Input schema
{
  "type": "object",
  "required": [
    "prdId",
    "cwd"
  ],
  "properties": {
    "prdId": {
      "type": "string",
      "description": "The ID of the PRD to get user stories for, PRD ID convention is PRD<PRD Number>, PRD number is zero padded with minimum 2 digits, e.g. PRD01, PRD12, PRD103, etc."
    },
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    }
  }
}
——
list-all-tasksList 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)
Input schema
{
  "type": "object",
  "required": [
    "cwd"
  ],
  "properties": {
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    },
    "limit": {
      "type": "number",
      "description": "Limit the number of documents to return, default is 10"
    },
    "offset": {
      "type": "number",
      "description": "Offset the number of documents to return, default is 0"
    }
  }
}
——
searchSearch 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)
Input schema
{
  "type": "object",
  "required": [
    "searchTerm",
    "cwd"
  ],
  "properties": {
    "searchTerm": {
      "type": "string",
      "description": "The search term to search for"
    },
    "type": {
      "type": "string",
      "description": "Optional type of document to search in, valid values are: PRD, BRD, NFR, UIR, TC, BP, US, TASK"
    },
    "cwd": {
      "type": "string",
      "description": "Absolute path where the tool is called from and containing the `.specifai-path` file to auto-infer the specifai project path. This path will be current working directory (cwd) from where the tool is called."
    }
  }
}
——
set-project-pathUpdate 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.
Input schema
{
  "type": "object",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "The absolute path to a directory containing specifai specification files."
    }
  }
}
——

Resources 0

  • None observed.

Resource templates 0

  • None observed.

Prompts 0

  • None observed.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

Specifai MCP Server questions

How do I install Specifai MCP Server?

Install the selected package version with: npm install --save-exact @presidio-dev/specifai-mcp-server@0.5.1

What tools does Specifai MCP Server provide?

Specifai MCP Server exposed 13 tools during independent protocol observation, including get-bpds, get-brds, get-nfrs, get-prds, get-task, get-task-by-id, get-tasks, get-tcs, and others.

Is Specifai MCP Server secure?

Our scanner tested version 0.5.1 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP Servers

Let’s talk about MCP security.

Share your details and our security team will contact you.