Autousers

Stdio bridge (Cline, Zed, Goose)

schedule4 mincalendar_todayLast updated 2026-04-28

Connect stdio-only MCP clients — Cline, Zed, Continue, Goose — to the Autousers remote server via the mcp-remote shim.

Some clients only support stdio-based MCP servers. The mcp-remote package by @geelen bridges the gap — it spawns a local stdio server that proxies to a remote HTTP+SSE endpoint and handles OAuth via a local browser.

warningPin mcp-remote >=0.1.16 to pick up the fix for CVE-2025-6514 (open redirect in the local OAuth callback).

Base config snippet

{
  "mcpServers": {
    "autousers": {
      "command": "npx",
      "args": ["-y", "mcp-remote@>=0.1.16", "https://mcp.autousers.ai/mcp"]
    }
  }
}

Use this snippet in your client's MCP config file

Cline (VS Code extension)

Open the Cline MCP settings file and add the snippet.

  • macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
  • Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
  • Or use Cline's MCP settings panel in the VS Code sidebar.

Zed

Add a context_servers entry to ~/.config/zed/settings.json.

{
  "context_servers": {
    "autousers": {
      "command": {
        "path": "npx",
        "args": ["-y", "mcp-remote@>=0.1.16", "https://mcp.autousers.ai/mcp"]
      }
    }
  }
}

~/.config/zed/settings.json

Continue.dev

Add an mcpServers entry to ~/.continue/config.yaml.

mcpServers:
  - name: autousers
    command: npx
    args:
      - -y
      - "mcp-remote@>=0.1.16"
      - https://mcp.autousers.ai/mcp

~/.continue/config.yaml

Goose

In the Goose extensions UI, add a new stdio extension with the same command and args as the base snippet above. If Goose supports remote MCP natively, use the URL https://mcp.autousers.ai/mcp directly instead.

Was this article helpful?