io.github.Inflectra/mcp-server-spira
A Model Context Protocol (MCP) server enabling AI assistants to interact with Spira by Inflectra.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
mcp-server-spiraclaude mcp add mcp-server-spira -e 'INFLECTRA_SPIRA_BASE_URL=<INFLECTRA_SPIRA_BASE_URL>' -e 'INFLECTRA_SPIRA_USERNAME=<INFLECTRA_SPIRA_USERNAME>' -e 'INFLECTRA_SPIRA_API_KEY=<your inflectra_spira_api_key>' -- uvx mcp-server-spira==1.1.1
{
"mcpServers": {
"mcp-server-spira": {
"command": "uvx",
"args": [
"mcp-server-spira==1.1.1"
],
"env": {
"INFLECTRA_SPIRA_BASE_URL": "<INFLECTRA_SPIRA_BASE_URL>",
"INFLECTRA_SPIRA_USERNAME": "<INFLECTRA_SPIRA_USERNAME>",
"INFLECTRA_SPIRA_API_KEY": "<your inflectra_spira_api_key>"
}
}
}
}
Environment variables
INFLECTRA_SPIRA_BASE_URLrequired The base URL for your instance of Spira (typically https://mycompany.spiraservice.net or https://demo-xx.spiraservice.net/mycompany)INFLECTRA_SPIRA_USERNAMErequired The login name you use to access SpiraINFLECTRA_SPIRA_API_KEYrequired secret The API Key (RSS Token) you use to access the Spira REST API
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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:
pip install mcp-server-spira
Add to your MCP client config:
{
"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:
mcp install src/mcp_server_spira/server.py --name "Inflectra Spira Server"
Configuration
Set these environment variables (or use a .env file):
| Variable | Required | Description |
|---|---|---|
INFLECTRA_SPIRA_BASE_URL | Yes | Base URL for your Spira instance |
INFLECTRA_SPIRA_USERNAME | Yes | Your Spira login name |
INFLECTRA_SPIRA_API_KEY | Yes | API Key (RSS Token) from your Spira user profile |
SPIRA_PROJECT_ID | No | Default product ID — avoids passing product_id on every call |
SPIRA_CREATE_TAGS | No | Comma-separated tag string merged into Tags on every artifact the MCP creates; empty or unset disables injection |
SPIRA_UPDATE_TAGS | No | Comma-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
| Tool | Description |
|---|---|
mywork_search_artifacts | Your assigned items (task, incident, requirement, test_case, test_set) with filtering and field projection |
product_search_artifacts | Search artifacts in a product (11 types). Supports cross-product fan-out, server-side filtering, and nested sub-artifact includes. |
product_get_artifact | Single artifact by ID with full details and optional sub-artifact includes |
program_search_artifacts | Search program-level artifacts (capability, milestone) |
Write Tools
| Tool | Description |
|---|---|
product_create_artifact | Create artifacts (incident, task, requirement, test_case, risk, release, test_set, build, test_step, mitigation, requirement_step) |
product_update_artifact | Update existing artifacts |
product_record_test_run | Record automated test results from CI/CD |
create_comment | Add a comment to an artifact |
create_association | Link two artifacts (related-to, depends-on, coverage) |
Workspace & Configuration Tools
| Tool | Description |
|---|---|
workspace_search | List products, programs, or product templates with field projection |
workspace_get | Get a single product, program, or template by ID |
template_get_metadata | Types, statuses, priorities, severities, custom properties, and more for a template |
get_artifact_schema | Field 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
Frequently asked questions
What is io.github.Inflectra/mcp-server-spira?
A Model Context Protocol (MCP) server enabling AI assistants to interact with Spira by Inflectra.
How do I install io.github.Inflectra/mcp-server-spira?
It runs on your machine. In Claude Code: claude mcp add mcp-server-spira -e 'INFLECTRA_SPIRA_BASE_URL=<INFLECTRA_SPIRA_BASE_URL>' -e 'INFLECTRA_SPIRA_USERNAME=<INFLECTRA_SPIRA_USERNAME>' -e 'INFLECTRA_SPIRA_API_KEY=<your inflectra_spira_api_key>' -- uvx mcp-server-spira==1.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.Inflectra/mcp-server-spira need an API key?
Yes. It expects INFLECTRA_SPIRA_BASE_URL, INFLECTRA_SPIRA_USERNAME, INFLECTRA_SPIRA_API_KEY, which you set in its configuration.
Is io.github.Inflectra/mcp-server-spira open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.Inflectra/mcp-server-spira?
It is published by Inflectra. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.