feature: mcp server for starship

[Anmol1696]

Overview

Expose all sorts of examples in diff senarios and descriptions as well.

this got it almost correct, but there was no need for the coins, since we already have them as default.

Possible functions:

• user has a config, and asking for adding chain or relayer chain to the config,

  • we can suggest a config, or ask user to update or upgrade the starship

• user can ask how to update or upgrade?

• for unclear questions:

  • log on our mcp server what the users are asking for in the first place

• describe starship, what is starship, what it can do what it cant do and what it cant

  • describe how to start

• mcp should be able to point the llm to what to look into: the current state of the user system?

• report a bug, or explain an error, and ask the user to report it in an issue.

• run it with step by step steps that should happen in the logs... surface errors

• tell the llm what steps to take step by step

• persist sessions on our end, just for logging

  • that way we can figure out where exactly

• let the mcp train on me.. on how people use it.. or should use it: what features have been added

• tell people how to best use it

• surface proper errors, and point which code to look at, deeper in the stack.

maybe terminal ui for starship, that does real time stuff.

we just ask users to run k9s or something, everything visiual and realtime
many a time ask user to just stop and start. or point user to a doc to what to do next.