Other AI apps

What your app needs

• Remote MCP over Streamable HTTP. Sidekick for AI runs on the web; there’s nothing to install or run on your computer. Apps that only run local servers can use the mcp-remote bridge.
• OAuth sign-in. The app opens a sign-in page, you sign in with Google, and the app gets its own access to Sidekick for AI. It never receives your Google password or your Google sign-in.

Claude Code

Add Sidekick for AI as a remote HTTP server:

claude mcp add --transport http sidekick https://mcp.heysidekick.app/mcp

Then run /mcp in Claude Code, choose sidekick and Authenticate to sign in.

VS Code

Add Sidekick for AI to your MCP configuration (.vscode/mcp.json in a project, or your user configuration), then start it from the file and sign in when VS Code asks:

{
  "servers": {
    "sidekick": {
      "type": "http",
      "url": "https://mcp.heysidekick.app/mcp"
    }
  }
}

Any other app

Look for “add MCP server”, “custom connector” or “remote server” in its settings, and use https://mcp.heysidekick.app/mcp.

Apps that only run local servers

If the app can only start a server on your computer, use the mcp-remote bridge as the server’s command. It needs Node.js 20.18 or later.

npx -y mcp-remote https://mcp.heysidekick.app/mcp

In an app that’s set up with a JSON file, that’s:

{
  "mcpServers": {
    "sidekick": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.heysidekick.app/mcp"]
    }
  }
}

• The first time, a browser opens for you to sign in with Google.
• The bridge shows as “MCP CLI Proxy” on the sign-in page and your account page. The sign-in page also says its name isn’t verified and that access goes to localhost. That’s expected: it’s the bridge on your own computer, passing requests to Sidekick for AI.
• Its sign-in is saved in ~/.mcp-auth, so it doesn’t ask again. Every app that uses the bridge with this address shares that one sign-in. To use a different Google account, delete that folder.