Thanks for the PR, @hhovsepy !
I've added some comments.

LGTM

Tests passed, also I've done some manual testing using the inspector:

Thanks for this — the structure is clean (the listResourceHandler factory is a nice touch), the README/docs/configuration.md regenerate with no drift, and build/vet/the kiali suite all pass.

Reviewing from the kubernetes-mcp-server side — Kiali owns the toolset's deeper behavior and its own tests, so I've kept this to three things worth a look before merge:

1. traffic-topology can fail on its default no-arg invocation — get_mesh_traffic_graph marks namespaces required, but the prompt makes it optional and hard-fails when omitted.
2. Generic prompt names — list-namespaces / list-services / list-workloads aren't mesh-qualified; with core + kiali enabled they read like core cluster ops, and this will only get worse as core adds its own prompts.
3. service-troubleshoot hardcodes a -v1 workload suffix — fine for bookinfo, empty logs for most real services.

Not flagging test coverage — assuming that's handled in the Kiali repo.

Thanks for the iterations, @hhovsepy — the prompt naming and the -v1 workload suffix from my earlier review are both sorted. josunect's threads are all resolved and the suite/docs are clean.

One thing left before this is good to go — it's the other half of my original traffic-graph comment:

mesh-topology ships with its traffic-graph section permanently empty. meshTopologyHandler calls get_mesh_traffic_graph with no namespaces, but that endpoint requires them, so the section always degrades to (data unavailable: …). traffic-topology already solves this with resolveNamespaces — same fix applies here (details inline). That's the only blocker from my side.

Non-blocking polish, take it or leave it:

• "all mesh namespaces" in the traffic-topology arg/error/README actually means all accessible namespaces — minor wording.
• A one-line comment on fetchKialiData to mark the soft-fail intentional (it's what hid the issue above).
• A mesh-topology test would've caught this — worth one with the fix, though I'm leaving broader coverage to the Kiali repo.

Fix the mesh-topology graph and I'm happy to approve.

Thanks @hhovsepy — all my review points are addressed. mesh-topology now resolves namespaces before the traffic-graph call (with TestMeshTopologyPrompt covering it), and the wording and fetchKialiData doc comment are in too. Verified build/vet/the Kiali suite locally. LGTM.