Epic Goal

Investigate areas for potential improvements to the MCP server support in Backstage. Looking at a few areas in particular:

• Adding support for audit logging to the MCP server 
• Integration with the Backstage eventing/notification framework
• Handling write/destructive operations securely

Why is this important?

• The MCP server support in Backstage is still fairly basic, and we should look at ways to harden it for real-world use cases
• This provides us some avenues to eventually provide upstream contributions to the Backstage community, and allows us to get involved more generally with Backstage

Scenarios

1. Integrate audit logging into the MCP server in Backstage
   1. Stretch goal: Upstream contribution
2. Integrate the notification and eventing frameworks into the MCP server in Backstage
   1. Stretch goal: Upstream contribution
3. Investigate how to securely handle write/destructive operations through MCP tools
   1. The implementation task will be handled under RHDHPAI-1015

Acceptance Criteria (Mandatory)

• Proof of Concepts showing the following:
  • Audit logging successfully integrated into the MCP server
  • Event/notification system successfully integrated into the MCP server
  •  Secure write operations when using an MCP tool
• Stretch: Upstream contributions for the above

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment