Mcp Server Spira

io.github.InflectraPublished by GitHub account Inflectrav1.1.1Updated Oct 24, 2026

A Model Context Protocol (MCP) server enabling AI assistants to interact with Spira by Inflectra.

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Local MCP server that connects an AI assistant to Inflectra Spira for project, test and requirements management.

What you can do
  • Search and read artifacts: your assigned items, product artifacts across 11 types, program-level capabilities and milestones, single artifacts by ID
  • Create and update artifacts such as incidents, tasks, requirements, test cases, risks, releases, builds and test steps
  • Record automated test run results and add comments to artifacts
  • Link artifacts with associations such as related-to, depends-on and coverage
  • Browse the workspace: list or fetch products, programs and templates, and read template metadata
  • Inspect field schemas for artifact types locally without calling the API
When to use it
Useful when a team keeps its projects, requirements and test cases in SpiraTest, SpiraTeam or SpiraPlan and wants an assistant to query assigned work, search across products, or file and update artifacts and test results from chat or CI/CD.
Requirements
Runs locally as a Python package (pip install mcp-server-spira) over stdio, so Python is needed. Requires three environment variables: INFLECTRA_SPIRA_BASE_URL, INFLECTRA_SPIRA_USERNAME and INFLECTRA_SPIRA_API_KEY (an RSS token from the Spira user profile). Optional SPIRA_PROJECT_ID, SPIRA_CREATE_TAGS and SPIRA_UPDATE_TAGS. Network access to the Spira instance.
Before you install
The API key is a personal access token stored in the client config or a .env file, so protect it. Write tools create and update artifacts, record test runs, add comments and create associations in your Spira instance, and SPIRA_CREATE_TAGS or SPIRA_UPDATE_TAGS can silently add tags to everything the assistant writes. All queries and changes go to your Spira server.

Installation

In SourceWeft

  1. Open Mcp Server Spira in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MCP Inflectra Spira Server

A Model Context Protocol (MCP) server that lets AI assistants interact with Inflectra Spira — covering project management, test management, and requirements management.

Works with SpiraTest, SpiraTeam, and SpiraPlan.

Table of Contents

Quick Start

Install from PyPI:

bash
pip install mcp-server-spira

Add to your MCP client config:

json
{  "mcpServers": {    "inflectra-spira": {      "command": "python",      "args": ["-m", "mcp_server_spira"],      "env": {        "INFLECTRA_SPIRA_BASE_URL": "https://myinstance.spiraservice.net",        "INFLECTRA_SPIRA_USERNAME": "mylogin",        "INFLECTRA_SPIRA_API_KEY": "{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX}"      }    }  }}

For Cline, add "type": "stdio" to the server config. For Claude Desktop:

bash
mcp install src/mcp_server_spira/server.py --name "Inflectra Spira Server"

Configuration

Set these environment variables (or use a .env file):

VariableRequiredDescription
INFLECTRA_SPIRA_BASE_URLYesBase URL for your Spira instance
INFLECTRA_SPIRA_USERNAMEYesYour Spira login name
INFLECTRA_SPIRA_API_KEYYesAPI Key (RSS Token) from your Spira user profile
SPIRA_PROJECT_IDNoDefault product ID — avoids passing product_id on every call
SPIRA_CREATE_TAGSNoComma-separated tag string merged into Tags on every artifact the MCP creates; empty or unset disables injection
SPIRA_UPDATE_TAGSNoComma-separated tag string merged into Tags on every artifact the MCP updates; empty or unset disables injection

Available Tools

13 tools organized by scope. All data-retrieval tools return structured JSON with field projection, filtering, and a consistent response envelope.

Search Tools

ToolDescription
mywork_search_artifactsYour assigned items (task, incident, requirement, test_case, test_set) with filtering and field projection
product_search_artifactsSearch artifacts in a product (11 types). Supports cross-product fan-out, server-side filtering, and nested sub-artifact includes.
product_get_artifactSingle artifact by ID with full details and optional sub-artifact includes
program_search_artifactsSearch program-level artifacts (capability, milestone)

Write Tools

ToolDescription
product_create_artifactCreate artifacts (incident, task, requirement, test_case, risk, release, test_set, build, test_step, mitigation, requirement_step)
product_update_artifactUpdate existing artifacts
product_record_test_runRecord automated test results from CI/CD
create_commentAdd a comment to an artifact
create_associationLink two artifacts (related-to, depends-on, coverage)

Workspace & Configuration Tools

ToolDescription
workspace_searchList products, programs, or product templates with field projection
workspace_getGet a single product, program, or template by ID
template_get_metadataTypes, statuses, priorities, severities, custom properties, and more for a template
get_artifact_schemaField schema for any artifact type (local-only, no API call)

Usage Examples

Try these prompts with your AI assistant:

Show me my assigned tasks in Spira
List all products in my Spira instance
Get the open incidents in product 55
Search for critical requirements across products 55 and 60
Get the field schema for incidents

License

MIT — see LICENSE.

Built with MCP Python SDK · Spira REST API v7.0

Source: README.md at commit ebbc26f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts