[BUG] show the correct status for the MCPServer resource

[peterj]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct
• I am using the latest version of the software
• I have tried to clear cache/cookies or used incognito mode (if ui-related)
• I can consistently reproduce this issue

🎯 Affected Service(s)

Multiple services / System-wide issue

🚦 Impact/Severity

No impact (Default)

🐛 Bug Description

Just like we show the status of the agents when the pod is being created, we should show the same for the MCPServer resource.

When the pod is being created AND when it's being deleted.

The PR that added this functionality for agents: kagent-dev/kagent#737

🔄 Steps To Reproduce

1. Create a tool server

Notice there's no status on the tool server until the pod gets created. only then you see the tools. we need to show a "Not ready" status while the pod is being created.

2. Delete the tool server
   Same as above -- the entry is still in the list, without tools. WE should show "Deleting" status (or Not ready).

🤔 Expected Behavior

No response

📱 Actual Behavior

No response

💻 Environment

No response

🔧 CLI Bug Report

No response

🔍 Additional Context

No response

📋 Logs

📷 Screenshots

No response

🙋 Are you willing to contribute?

• I am willing to submit a PR to fix this issue

[EItanya]

I am going to transfer this issue to kmcp

[inFocus7]

: +1 :

When going through a demo of kagent + kmcp, I noticed that the MCPServer status was Not Ready even if it worked. From the statuses, the failing one was: Ready: False -> PodsNotReady -> Deployment Not Ready: 0/0 replicas ready.

kmcp 0.1.5 ; kagent 0.6.3

[EItanya]

Most likely we just need to make this reconciler more tolerant of failure, and make sure it's retrying properly

[yashrajshuklaaa]

hey @EItanya is this issue still open?
if yes pls assign me this one

[tmohanvamsi]

Hi, I'd like to work on this. I'll look at kagent#737 as the reference
implementation and apply the same status pattern to the MCPServer controller.
Will open a draft PR shortly.