Value Statement

The  MCP Server will have the same RBAC constructs as of the Search API in future as indicated in ACM-25764 . However for Dev Preview, we should at least check if the user has cluster admin privelege. If so, proceed to get data. If not, return permission not granted.

Definition of Done for Engineering Story Owner (Checklist)

• The MCP Server can be deployed on a Hub cluster and queried from OLS ,claude code etc
• The RBAC permissions of the user should be honored.
• Code is checked into a repo
• Bonus - Konflux build

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.