1jehuang / 1jehuang/jcode

Feature: /mcp slash command to enable/disable MCP servers

Open
#835 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

autonomous: no enhancement triage: needs-decision
Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
2d 7h
Merged PRs (30d)
30

Description

Summary

Add a /mcp slash command to the TUI that lets users toggle MCP servers on/off interactively. The toggle state persists to ~/.jcode/mcp.json (opencode-style) and refreshes the manager in-memory config and UI state immediately after each toggle.

Problem

Today there is no way to enable or disable an individual MCP server from the TUI without editing the config file and restarting. Users who run several MCP servers have no quick way to temporarily silence a noisy or broken server during a session.

Proposal

  • /mcp slash command opens a toggle list of configured MCP servers.
  • Toggling writes the enabled/disabled flag to ~/.jcode/mcp.json so it survives restarts.
  • The manager in-memory config and the info-widget UI state refresh immediately after each toggle.

Implementation

A working implementation is ready for review on the feature/mcp-server-toggles branch (rebased onto latest master, 465 insertions across 15 files, jcode-app-core + jcode-tui build, mcp + info_widget + slash_command tests pass).

@1jehuang would be great if you could take a look.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the existing implementation on the feature/mcp-server-toggles branch, focusing on jcode-app-core, jcode-tui, mcp, info_widget, and slash_command tests. Run the listed builds and tests, then verify that toggling a configured MCP server persists to ~/.jcode/mcp.json and refreshes the in-memory and UI state immediately.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.