Skip to main content
Use this guide when you want a single, predictable setup path per client.
This page is operational (how-to). For architecture and transport choices, see MCP Server Styles.

Endpoint Map and Auth Expectations

Optional Local Browser Automation (Chrome DevTools MCP Fork)

Add this local server if you want browser automation tools:

Client Workflows

Install

Plugin setup auto-adds: chrome-devtools, char-docs, webmcp-docs, char-saas.

Manual fallback (no plugin)

Verify

Use in chat

  • Ask for docs/tool calls normally; Claude will select tools when relevant.
  • Use aliases in prompts when you want to force source selection (for example, char-docs vs webmcp-docs).

Manage and troubleshoot

  • Re-run /char:setup if plugin-managed servers drift.
  • Remove and re-add a failing server if it remains disconnected.
  • For char-saas, finish browser auth before retrying MCP tools.

Scope options (local, project, user)

Codex CLI

Install

Verify

Use in chat

  • Prompt normally and reference server aliases when you want explicit routing.

Manage and troubleshoot

  • If a server is missing or stale, run the add command again.
  • Complete char-saas auth in browser when prompted.

Gemini CLI

Configure (~/.gemini/settings.json)

Verify

  • Start Gemini CLI and run /mcp to confirm servers are registered and connected.

Use in chat

  • Ask normally; include endpoint aliases in prompts when needed.

Manage and troubleshoot

  • Re-open Gemini CLI after editing settings.json.
  • Re-auth char-saas if tool calls return 401.

Cursor

One-click add (char-saas)

Add Char SaaS in Cursor

Manual config (.cursor/mcp.json)

Verify

  • Open Cursor MCP settings and confirm each server reports connected/ready.

Use in chat

  • Use Agent mode and run prompts normally; tools are auto-selected when relevant.

Manage and troubleshoot

  • Restart Cursor after editing MCP config files.
  • Check server status/logs in MCP settings before re-adding servers.

VS Code + GitHub Copilot

One-click add (char-saas)

Add Char SaaS in VS Code

Manual config (.vscode/mcp.json)

Verify

  • Run MCP: List Servers from Command Palette.

Use in chat

  • Open Copilot Chat, switch to Agent mode, and confirm tools are available.

Manage and troubleshoot

  • Re-open VS Code window after config edits.
  • Re-run auth for char-saas when prompted.

Windsurf

Install (~/.config/codeium/windsurf/mcp_config.json)

Verify

  • Check MCP server status in Windsurf MCP settings.

Use in chat

  • Use Cascade normally; MCP tools should be available automatically.

Manage and troubleshoot

  • Restart Windsurf after config edits.
  • Use MCP server status/log views for connection failures.

UI-managed clients (ChatGPT, Claude Desktop, Claude.ai)

  • Add a custom remote MCP server in client settings.
  • Prefer https://app.usechar.ai/mcp for full Char SaaS access.
  • Complete browser auth when prompted.

Quick Verification Checklist

  1. Endpoint aliases appear in your client/server list.
  2. char-docs and webmcp-docs respond without auth prompts.
  3. char-saas completes auth and no longer returns 401.
  4. Optional chrome-devtools server is connected when browser tooling is needed.

Sources