Mcp Server Spira
Let your agent read and update Spira requirements, releases, defects, and test artifacts from Inflectra ALM.
Overview
io.github.Inflectra/mcp-server-spira is a MCP server for the Build phase that lets AI assistants interact with Inflectra Spira ALM using your instance URL and API key.
What is this MCP server?
- Connect AI assistants to Inflectra Spira via MCP over stdio
- Authenticate with instance URL, username, and Spira REST API key (RSS token)
- PyPI package mcp-server-spira at version 1.1.1
- Supports customer or demo Spirаservice.net instances
- Keeps requirements and testing context inside the agent loop
- Server version 1.1.1
- PyPI identifier mcp-server-spira
- Three required env vars: base URL, username, API key
What problem does it solve?
Your agent cannot plan or fix work against Spira when requirements and tests only exist inside the Spira web app.
Who is it for?
Small teams or solo builders already paying for Spira who want MCP-driven backlog and test management from the IDE.
Skip if: Builders on Linear, Jira-only, or no ALM stack who would need to adopt Spira first.
What do I get? / Deliverables
After configuration, the agent can work with Spira data in chat—reducing context switching while you build and maintain traceability.
- Agent-accessible Spira project and artifact context
- Updates to Spira entities performed via REST through MCP
- Reduced copy-paste between IDE and Spira UI
Recommended MCP Servers
Journey fit
Spira is where backlog, requirements, and test traceability live during active product construction, so Build is the primary journey shelf. PM fits best because the MCP bridges ALM entities—stories, tasks, incidents, and test cases—rather than shipping infrastructure or marketing.
How it compares
Spira ALM MCP connector, not a standalone project-management skill or test runner.
Common Questions / FAQ
Who is io.github.Inflectra/mcp-server-spira for?
Developers using Inflectra Spira who want Claude, Cursor, or Codex to read and update ALM items without leaving the coding session.
When should I use io.github.Inflectra/mcp-server-spira?
During Build-phase PM when you draft requirements, link tests, triage defects, or summarize release status from live Spira data.
How do I add io.github.Inflectra/mcp-server-spira to my agent?
Install mcp-server-spira from PyPI, set SPIRA base URL, username, and INFLECTRA_SPIRA_API_KEY, then add the stdio MCP entry in your agent config.