Skip to main content
Glama

Spira MCP

Read-only Cursor MCP for daily Spira incident reviews against https://<OrgID>.spiraservice.net.

What it does

  • incident_daily_digest — markdown digest of incidents filtered by product, status, owner, detected release, and optional incident IDs; includes description, last N comments, and attachment metadata (AttachmentIds)

  • list_incident_filter_options — statuses, owners, and releases for picking filter labels

  • list_incident_attachments — list documents on a single incident

  • download_incident_attachment — download a file attachment into a local cache directory and return the absolute path (for agent Read / vision); URL attachments return the URL without writing a file

No create/update/delete/upload tools. Local filesystem writes are limited to the attachment cache.

Related MCP server: Swarmia MCP Server

Install

pip install -e ".[dev]"
pytest

Cursor MCP config

Add to %USERPROFILE%\.cursor\mcp.json (fill in org URL, username + RSS token):

{
  "mcpServers": {
    "spira": {
      "command": "C:\\Program Files\\Python311\\python.exe",
      "args": ["-m", "spira_mcp"],
      "env": {
        "INFLECTRA_SPIRA_BASE_URL": "https://<OrgID>.spiraservice.net",
        "INFLECTRA_SPIRA_USERNAME": "YOUR_LOGIN",
        "INFLECTRA_SPIRA_API_KEY": "{YOUR-RSS-TOKEN}",
        "SPIRA_COMMENT_LIMIT": "5",
        "SPIRA_MAX_INCIDENTS": "50",
        "SPIRA_ATTACHMENT_MAX_BYTES": "5242880",
        "SPIRA_ATTACHMENT_ALLOW_LARGE_FS": "false"
      }
    }
  }
}

Optional:

  • "SPIRA_PRODUCT_ID": "123" (numeric only) or "SPIRA_PRODUCT_NAME": "My Product" for a default product

  • "SPIRA_ATTACHMENT_CACHE_DIR": "D:\\spira-cache" — override cache root (default: {cwd}/.spira-attachments, gitignored)

  • "SPIRA_ATTACHMENT_MAX_BYTES": "5242880" — soft metadata gate and hard stream ceiling (default 5 MiB)

  • "SPIRA_ATTACHMENT_ALLOW_LARGE_FS": "true" — allow writing attachments larger than the soft cap (disables the hard stream ceiling)

Restart Cursor MCP (or reload) after saving.

Example prompts

  • “Run an incident digest for status Open, owner me, detected release 25.7”

  • “Digest incident IDs 1201, 1205 for our default product”

  • “Show filter options for the default Spira product”

  • “List attachments on incident 1201, then download attachment 88 and summarize the screenshot”

Design

See docs/superpowers/specs/2026-07-28-incident-daily-digest-design.md.

A
license - permissive license
Not graded
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables querying Swarmia's Export API for engineering metrics including pull request analytics, DORA metrics, investment balance, and effort reporting through an MCP interface.
    8
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for querying resolved Jira tickets across multiple Atlassian Cloud sites, enabling executive summarization of development activity.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for investigating cloud incidents and managing approvals. Provides read-only tools to list incidents, investigate incidents, and list approvals, keeping remediation behind human approval.
    MIT

View all related MCP servers

Related MCP Connectors

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/satish-bhindi/Spira-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server