Skip to content

Remove mcp command - it's no longer needed with modern MCP setup #207

@camoneart

Description

@camoneart

Current Situation

The mst mcp serve command has become obsolete with the introduction of the modern claude mcp add command. Users no longer need to manually start the MCP server.

Problem

  • Users run claude mcp add to register MCP servers
  • Claude Code automatically manages the server lifecycle
  • The mst mcp command serves no practical purpose anymore
  • It adds unnecessary complexity to the CLI

Proposed Solution

  1. Remove the mcp command entirely from the CLI
  2. Keep MCP integration documentation in README
  3. This would be a breaking change requiring v4.0.0

Benefits

  • Simpler, cleaner CLI
  • Less confusion for users
  • Reduced maintenance burden

Migration Guide

Users currently using mst mcp serve should switch to one of the following, depending on their needs:

Local Scope (Default - only for current project, private to you)

claude mcp add maestro -s local -- npx -y @camoneart/maestro mcp serve
# Or without -s flag (local is default)
claude mcp add maestro -- npx -y @camoneart/maestro mcp serve

Project Scope (saved in .mcp.json for team sharing via version control)

claude mcp add maestro -s project -- npx -y @camoneart/maestro mcp serve

User Scope (available across all projects on the machine, private to your user)

claude mcp add maestro -s user -- npx -y @camoneart/maestro mcp serve

Note: For users who have globally installed maestro, replace npx -y @camoneart/maestro with just maestro.

Questions

  • Should we proceed with this removal?
  • Any concerns about breaking existing workflows?
  • Should we deprecate first in v3.x before removing in v4.0.0?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions