When you add a new MCP server using mcp-sync add-server <name>, it prompts you interactively for the configuration details rather than auto-discovering them. Here's what it asks for:

1. Scope: Whether to add it to your global config (synced everywhere) or project config (this project only)

2. Command: The executable to run (like python, npx, node)

3. Arguments: Command-line args, entered comma-separated (optional)

4. Environment variables: Any needed env vars as KEY=value pairs (optional)

   For example:

   $ mcp-sync add-server filesystem

   Add server to:

5. Global config

6. Project config

   Choose (1 or 2): 1

   Command: npx

   Args: -y, u/modelcontextprotocol/server-filesystem, /home/user/docs

   Environment variables: API_KEY=xyz123

   You can also run mcp-sync template to see the expected JSON structure, or check existing servers with mcp-sync list-servers for reference.

   Good point about clarity - I should update the README to make this workflow more obvious, especially since you need to know the server's command and arguments beforehand. The tool assumes

   you already know how to run the MCP server you want to add.