AI-assisted development is moving beyond code generation and project research. The latest Spira MCP Server release brings AI assistants closer to the operational work of software delivery by enabling interaction with the work items held in Spira.
For enterprise teams, the significance is the connection between AI activity in a developer’s working environment and the ALM records used to coordinate delivery. Spira remains the place where work is defined, organized, and discussed. The MCP Server now gives supported AI assistants a way to participate in those activities.
From project research to interactive ALM work
Previously, AI assistants connected through the Spira MCP Server could retrieve project data from Spira. That supported research-oriented tasks, such as understanding the project information available to a development team.
This release adds interactive capabilities. AI assistants can now:
- Create work items in Spira
- Update existing work items
- Organize work items
- Collaborate on work items
- Retrieve project information as part of the same interaction
The capability applies to the growing set of AI-powered development environments referenced by Inflectra, including Claude Code, Cursor, Kiro, GitHub Copilot, and Visual Studio Code with AI agents such as Cline. The strategic point is less about any individual assistant and more about the controlled role Spira can play as the ALM environment connected to those assistants.
AI-assisted creation and updates of work items
Creating and updating work items directly from an AI-enabled development workflow can reduce the gap between technical discussion and recorded delivery work. When a team uses Spira to manage application work, the work item remains connected to the project context already stored in the ALM platform.
Enterprise example: During planning for a regulated application release, a senior engineer uses an AI assistant to review relevant project information in Spira and create a work item for a required implementation activity. The item enters the organization’s established Spira workflow, where delivery leaders can review the work alongside other release commitments.
Day-to-day team example: A developer investigating a reported issue uses an AI assistant in their coding environment to retrieve related Spira information and update the relevant work item with the current status. The developer avoids manually switching between disconnected research and work-recording steps, while the work remains visible to colleagues operating in Spira.
For QA and release management, this matters because work item quality affects planning, execution, and executive reporting. Teams need clear practices for deciding when AI-generated work item content is ready for use, who reviews it, and how it is incorporated into existing project processes.
Organizing work around the delivery process
The release also enables AI assistants to organize work items. In large programs, organization is a delivery-management concern. Product, engineering, QA, and release teams depend on work being structured in ways that support planning and coordination.
Enterprise example: A portfolio team preparing a major release has a large set of related implementation activities in Spira. An AI assistant can help organize those work items while operating within the project environment that delivery stakeholders use to coordinate release scope. Program leaders retain a consistent view of the work supporting the release.
Day-to-day team example: A QA lead working through a regression cycle asks an AI assistant to help organize the work items associated with the cycle. The lead can focus on validating the resulting structure and assigning follow-up activity, instead of spending time on repetitive administrative handling.
Mature teams should define the organizing conventions that matter to their operating model before broad adoption. Those conventions may include how teams group work for releases, how they handle status updates, and when a human owner must review changes. The feature provides interaction capability; effective use depends on disciplined workflows around it.
Collaboration inside the ALM environment
AI assistants can now collaborate on work items in Spira. This creates an opportunity to bring AI-supported contributions into the same environment where teams coordinate delivery decisions and project records.
Enterprise example: A distributed engineering organization uses Spira as the common ALM system for several teams contributing to a shared release. AI-assisted work item collaboration can support a common record of delivery activity across those teams, which helps release leadership evaluate progress using the project data held in Spira.
Day-to-day team example: A developer and tester are working through an item that requires clarification. An AI assistant can help interact with the item while team members continue their collaboration in Spira. The project record stays central to the discussion and follow-up work.
A deliberate adoption path for enterprise teams
Interactive AI access to ALM work deserves the same operational attention as any change to delivery workflows. Leaders should begin with a focused use case, such as creating work items from an approved development workflow or updating a defined class of delivery records. Teams can then assess the quality, consistency, and review effort associated with AI-assisted interactions.
Recommended next steps include:
- Identify a pilot workflow where Spira work item interaction has clear value.
- Define review and accountability practices for AI-created or AI-updated records.
- Involve development, QA, DevOps, and release-management stakeholders in the rollout.
This release matters because it connects AI-enabled development tools to the ALM work that drives enterprise software delivery. Merito can help teams fast-track Spira MCP Server adoption by identifying appropriate pilot workflows, mapping the capability to existing QA and DevOps practices, and establishing practical governance for AI-assisted work item management. Leaders can use this approach to introduce the capability with defined ownership, measurable workflow outcomes, and a clear path for broader adoption.