[Feedback]: Show mcp status on chat interface

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
shell
Domain
desktop

Research direction

Start by locating the chat interface and the existing MCP server settings or connection handling. Define the visible aggregate status for all MCP servers and the clickable overview of each server's availability; the work is done when users can identify unavailable servers without opening settings.

Written by the indexing model from the issue text.

Description

enhancement
What problem are you trying to solve?

I worked with command code desktop do communicate with a mcp server (the one of n8n, if it matters).
The command took suspiciously long and was reasoning a lot. I suspected the longcat 2 free model.

I switched to glm 5.3 flash and then saw steps like "ping 127.0.0.1" after a while, which also made me suspisious, but also after doing this like 30 times it never came to a conclusion.
I then switched to deepseek v4 flash and it then gave me the info that it could not reach the mcp server.

GLM flash wasted ~1 $ in credeits for this

What I am looking for would be a MCP status indication direct in the visible area of the chat (eg. like in the following mockup and not hidden in the settings:

Image

If you click on it, it shoud show an overview of the mcp servers and the deteils, you you might see which one is unavailible.

Maybe to have the "status light" be green/yellow/red, depending if all MCPs are availible (green), some are availible (yellow) and none are avilible (red)

What would improve it?

Save tokens and time

What do you do today?

No response

Product area

None

Dominant language
Shell
Stars
80
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CommandCodeAI/desktop

All issues in CommandCodeAI/desktop

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.