CLI Integration for MCP

The Sypha Command Line Interface supports robust MCP server integration, though it utilizes a configuration pathway distinct from the IDE extension.

Environment Paths

[!NOTE] Settings configured within the VS Code UI are not inherited by the CLI environment automatically.

Mapping Your Servers

Update your configuration at ~/.sypha/cli/global/settings/mcp_settings.json:

{
  "mcpServers": {
    "custom-server": {
      "command": "node",
      "args": ["/absolute/path/to/script.js"],
      "env": {
        "SERVICE_KEY": "your_secure_key"
      },
      "alwaysAllow": ["specific-tool-name"]
    }
  }
}

Cloud-Resident Servers (HTTP)

For hosted infrastructure, implement the streamable-http type:

{
  "mcpServers": {
    "cloud-infrastructure": {
      "type": "streamable-http",
      "url": "https://api.sypha.ai/mcp",
      "headers": {
        "Authorization": "Bearer your_token"
      }
    }
  }
}

Local Project Overrides

You can define project-specific servers by including an mcp.json file inside the .sypha directory at your project's root. These project-level definitions will take precedence over global CLI settings.

Managing Approvals

You can bypass manual tool confirmation for the CLI by enabling the following environment variable:

export SYPHA_AUTO_APPROVAL_MCP_ENABLED=true

Alternatively, leverage the alwaysAllow property within your configuration JSON to specifically whitelist individual tools.