io.github.Inflectra/mcp-server-spira
A Model Context Protocol (MCP) server enabling AI assistants to interact with Spira by Inflectra.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
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>"
}
}
}
}Variables d'environnement
INFLECTRA_SPIRA_BASE_URLobligatoire The base URL for your instance of Spira (typically https://mycompany.spiraservice.net or https://demo-xx.spiraservice.net/mycompany)INFLECTRA_SPIRA_USERNAMEobligatoire The login name you use to access SpiraINFLECTRA_SPIRA_API_KEYobligatoire secret The API Key (RSS Token) you use to access the Spira REST API
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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-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 |
|---|---|---|
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 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
Questions fréquentes
Qu'est-ce que io.github.Inflectra/mcp-server-spira ?
A Model Context Protocol (MCP) server enabling AI assistants to interact with Spira by Inflectra.
Comment installer io.github.Inflectra/mcp-server-spira ?
Il s'exécute sur votre machine. Dans 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. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.Inflectra/mcp-server-spira ?
Oui. Il attend INFLECTRA_SPIRA_BASE_URL, INFLECTRA_SPIRA_USERNAME, INFLECTRA_SPIRA_API_KEY, à renseigner dans sa configuration.
io.github.Inflectra/mcp-server-spira est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.Inflectra/mcp-server-spira ?
Il est publié par Inflectra. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.