Inflectra Spira MCP Server
OfficialThis MCP server lets AI assistants interact with Inflectra Spira for project, test, and requirements management.
Search your assigned work items (tasks, incidents, requirements, test cases, test sets) with filtering and field projection.
Search and retrieve artifacts across products and programs, including nested includes and cross-product searches.
Create and update Spira artifacts such as incidents, tasks, requirements, test cases, risks, releases, builds, and test steps.
Record automated test runs and CI/CD build results.
Add comments to artifacts and create associations/links between artifacts.
List and get products, programs, and product templates.
Fetch template metadata such as types, statuses, priorities, severities, custom properties, importances, probabilities, and impacts.
Retrieve local field schemas for artifact types without an API call.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Inflectra Spira MCP Server Show me my assigned tasks in Spira"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: TestRail MCP Server
Quick Start
Install from PyPI:
pip install mcp-server-spiraAdd 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 |
| Yes | Base URL for your Spira instance |
| Yes | Your Spira login name |
| Yes | API Key (RSS Token) from your Spira user profile |
| No | Default product ID — avoids passing |
| No | Comma-separated tag string merged into |
| No | Comma-separated tag string merged into |
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 |
| Your assigned items (task, incident, requirement, test_case, test_set) with filtering and field projection |
| Search artifacts in a product (11 types). Supports cross-product fan-out, server-side filtering, and nested sub-artifact includes. |
| Single artifact by ID with full details and optional sub-artifact includes |
| Search program-level artifacts (capability, milestone) |
Write Tools
Tool | Description |
| Create artifacts (incident, task, requirement, test_case, risk, release, test_set, build, test_step, mitigation, requirement_step) |
| Update existing artifacts |
| Record automated test results from CI/CD |
| Add a comment to an artifact |
| Link two artifacts (related-to, depends-on, coverage) |
Workspace & Configuration Tools
Tool | Description |
| List products, programs, or product templates with field projection |
| Get a single product, program, or template by ID |
| Types, statuses, priorities, severities, custom properties, and more for a template |
| 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 SpiraList all products in my Spira instanceGet the open incidents in product 55Search for critical requirements across products 55 and 60Get the field schema for incidentsLicense
MIT — see LICENSE.
Built with MCP Python SDK · Spira REST API v7.0
Available Tools
13 toolscreate_associationA
Link two artifacts. association_type: related-to, depends-on, coverage.
Valid source->dest (related-to/depends-on): document->automation_host,incident,release,requirement,risk,task,test_case,test_run,test_set,test_step; incident->incident,requirement,risk,task,test_step; release->release,requirement; requirement->incident,release,requirement,risk; risk->incident,requirement,risk,test_case; task->incident,task; test_case->risk,task. Coverage: release->test_case, requirement<->test_case, requirement->test_step.
Inputs: dest_artifact_id (required), dest_artifact_type (required), source_artifact_id (required), source_artifact_type (required… Returns: result
create_commentB
Add a comment to an artifact.
Use product_get_artifact with include=["comments"] to read existing comments.
Inputs: text (required), artifact_id (required), artifact_type (required), product_id. Returns: result
get_artifact_schemaARead-only
Returns the field schema for a Spira artifact type as JSON.
artifact_type: task, incident, requirement, test_case, release, risk, test_set, test_run, automation_host, capability, milestone Returns: {artifact_type, fields: [{name, type, description}]} or {error, valid_types}.
Inputs: artifact_type (required). Returns: result
mywork_search_artifactsCRead-only
Retrieve the current user's assigned artifacts.
artifact_type: [incident, task, test_case, requirement, test_set]
Inputs: limit, fields, offset, status, +2 more. Returns: result
product_create_artifactA
Create artifacts in a Spira product.
Name and Description are required for most types. Sub-artifacts (test_step, mitigation, requirement_step) require parent_id. Builds require release_id. Use get_artifact_schema to discover optional writable fields.
Inputs: fields (required), artifact_type (required), parent_id, product_id, +1 more. Returns: result
product_get_artifactARead-only
Retrieve a single artifact by ID from a Spira product.
artifact_type: incident|task|test_case|requirement|risk|release|test_set|test_run|automation_host|build|document release_id: required when artifact_type='build' include: test_steps (test_case), mitigations (risk), steps (requirement), comments (most types), associations (most types), coverage (requirement, test_case, release)
Inputs: artifact_id (required), artifact_type (required), include, product_id, +1 more. Returns: result
product_record_test_runB
Record an automated test result in Spira.
execution_status_id: 1=Failed, 2=Passed, 3=Not Run, 4=N/A, 5=Blocked, 6=Caution. test_case_id is the numeric ID without TC prefix (e.g. 12 for TC:12). short_message should be 50 chars or less.
Inputs: test_name (required), error_count (required), long_message (required), test_case_id (required), +3 more. Returns: result
product_search_artifactsBRead-only
Search artifacts in a Spira product.
filters: [{{"field": "Name", "operator": "contains", "value": "login"}}] — use get_artifact_schema for fields. release_id: required for builds.
Inputs: artifact_type (required), state, fields, status, +12 more. Returns: result
product_update_artifactA
Update a single artifact by ID in a Spira product.
Sub-artifacts (test_step, mitigation, requirement_step) require parent_id. Use get_artifact_schema to discover writable fields for each type. To clear a custom property, set its value to null.
Inputs: fields (required), artifact_id (required), artifact_type (required), parent_id, +1 more. Returns: result
program_search_artifactsCRead-only
Search artifacts in a Spira program.
artifact_type: [capability, milestone] program_id: required, no default
Inputs: program_id (required), artifact_type (required), fields, status, +4 more. Returns: result
template_get_metadataARead-only
Retrieves template metadata sections for a product template.
template_id: numeric ID (e.g. 45 for PT:45). metadata_type: sections to fetch (see enum). Omit for all. artifact_type: filter to one kind (e.g. "Requirement"). Omit for all. Some sections are artifact-specific (e.g. severities→Incident, importances→Requirement). Returns JSON: {template_id, sections, warnings}.
Inputs: template_id (required), artifact_type, metadata_type. Returns: result
workspace_getBRead-only
Retrieve a single workspace entity by its numeric ID.
workspace_type: 'product', 'program', 'product_template'
Inputs: workspace_id (required), workspace_type (required). Returns: result
workspace_searchCRead-only
Lists workspaces in Spira.
workspace_type: 'product', 'program', 'product_template'
Inputs: workspace_type (required), fields, program_id. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Most tools target distinct scopes/actions, but the presence of three search_artifacts tools (mywork, product, program) and several get-style tools (product_get_artifact, workspace_get, template_get_metadata, get_artifact_schema) creates some potential for misselection if the agent does not carefully check scope. The descriptions do help clarify boundaries, so confusion is limited to a few adjacent tools.
Names are predominantly snake_case and follow a scope_verb_noun pattern for product/program/template tools, but several tools omit the scope prefix (create_comment, create_association, get_artifact_schema) and workspace_search/workspace_get omit the resource noun. These are minor deviations in an otherwise predictable convention.
The 13 tools are well within a reasonable range for a multi-resource artifact management server, and each tool appears to serve a distinct role in search, retrieval, creation, updates, test recording, linking, commenting, or schema discovery. No tool feels redundant or extraneous.
The surface covers search/retrieval/creation/update across products, programs, workspaces, artifacts, comments, associations, and test runs, but lacks delete operations for artifacts, comments, and associations. These are minor gaps that agents can largely work around, but full lifecycle coverage would require them.
Maintenance
Related MCP Connectors
Create and manage test cases, test runs and results in Testiny from your AI assistant.
Manage Orangescrum projects, tasks, users, sprints, test cases, releases, and risks from AI tools.
Manage Loom projects, tasks, bugs, defects, clients and phases from AI assistants
Manage Redbooth tasks, task lists, comments, tags and files from Claude and other AI assistants.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with TestRail test management systems through comprehensive API integration. Supports retrieving and updating test cases, projects, suites, runs, and results, plus adding attachments and managing test data through natural language commands.1831 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact directly with TestRail instances for managing test projects, suites, cases, runs, results, plans, milestones, and attachments through the TestRail API with secure authentication.7755 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Targetprocess for search, create, update, and query of entities like User Stories and Bugs, with support for complex filters and data model discovery.MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with TestRail test management system, supporting full CRUD operations on projects, suites, sections, test cases, runs, results, plans, and milestones.35327 npm1MIT