This guide provides step-by-step instructions for adding custom MCP (Model Context Protocol) servers to Conductor when the UI doesn't provide a built-in option.
- Conductor (Claude Code) installed
- Terminal access
jqcommand-line JSON processor installed- MCP server package details (npm package name or command)
The Conductor UI only provides quick-add options for a few MCPs (Linear, Figma, Context7, Sentry). Custom MCPs need to be added manually to the configuration file.
cp ~/.claude.json ~/.claude.json.backupWhy: Always create a backup before modifying configuration files to prevent data loss.
jq '.mcpServers' ~/.claude.jsonExpected output: You should see existing MCPs like context7:
{
"context7": {
"args": ["-y", "@upstash/context7-mcp@latest"],
"command": "npx",
"env": {},
"type": "stdio"
}
}Replace <mcp-name> and <package-name> with your specific MCP details:
jq '.mcpServers += {"<mcp-name>": {"type": "stdio", "command": "npx", "args": ["-y", "<package-name>"], "env": {}}}' ~/.claude.json > ~/.claude.json.tmp && mv ~/.claude.json.tmp ~/.claude.jsonExample for Shopify MCP:
jq '.mcpServers += {"shopify-dev-mcp": {"type": "stdio", "command": "npx", "args": ["-y", "@shopify/dev-mcp@latest"], "env": {}}}' ~/.claude.json > ~/.claude.json.tmp && mv ~/.claude.json.tmp ~/.claude.jsonjq '.mcpServers' ~/.claude.jsonExpected output: You should see both the original and new MCP:
{
"context7": {
"args": ["-y", "@upstash/context7-mcp@latest"],
"command": "npx",
"env": {},
"type": "stdio"
},
"shopify-dev-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@shopify/dev-mcp@latest"],
"env": {}
}
}- Quit Conductor completely (Cmd + Q on macOS)
- Relaunch Conductor
Why: Configuration changes only take effect after a full restart.
Run this command to check MCP status:
claude mcp listExpected output:
Checking MCP server health...
context7: npx -y @upstash/context7-mcp@latest - ✓ Connected
shopify-dev-mcp: npx -y @shopify/dev-mcp@latest - ✓ Connected
jq '.mcpServers += {"shopify-dev-mcp": {"type": "stdio", "command": "npx", "args": ["-y", "@shopify/dev-mcp@latest"], "env": {}}}' ~/.claude.json > ~/.claude.json.tmp && mv ~/.claude.json.tmp ~/.claude.jsonFor locally installed MCP servers:
jq '.mcpServers += {"my-custom-mcp": {"type": "stdio", "command": "/path/to/mcp/server", "args": [], "env": {}}}' ~/.claude.json > ~/.claude.json.tmp && mv ~/.claude.json.tmp ~/.claude.jsonSolution:
- Verify the package name is correct
- Check that
npxcan install the package:npx -y <package-name> - Review Conductor logs for error messages
Solution:
- Restore from backup:
cp ~/.claude.json.backup ~/.claude.json - Verify JSON is valid:
jq '.' ~/.claude.json - Re-run the command carefully
Solution:
- Verify the MCP was added:
jq '.mcpServers' ~/.claude.json - Ensure you did a full quit and restart of Conductor
- Check for multiple Conductor processes:
ps aux | grep Conductor
- macOS/Linux:
~/.claude.json - Global MCP Key:
.mcpServers(affects all Conductor instances) - Project-level:
.localProjects["/path/to/project"].mcpServers(project-specific)
- MCP settings apply globally to all instances of Claude Code
- Project-level MCP configuration is not yet supported via UI
- Always backup before modifying configuration files
- The CLI command
claude mcp addmay not always work correctly for all MCPs - Manual JSON editing is the most reliable method currently
Last Updated: 2025-10-22 Tested On: Conductor (Claude Code) on macOS