MCP Clients

Client-specific setup instructions for connecting to GL Connector MCP servers. This page covers the most common MCP clients — for a comprehensive list of all MCP-compatible clients, see:

Example Clients - Model Context ProtocolModel Context Protocol

Clientsmodelcontextprotocol.info

New to GL Connector MCP? Start with the Quickstart for a fast setup using token-based auth, or the In-Depth Guide for OAuth 2.1 and other setup information.

Client Comparison Matrix

We have tested the following clients. For more clients, see the external references above.

Client

Transport

Token-based Auth

OAuth 2.1 (Native)

OAuth 2.1 (mcp-remote)

Requires Node.js

Notable Quirks

VSCode

Streamable HTTP

✅

⚠️ Unreliable

✅ Stable

Only for mcp-remote

—

Cursor

Streamable HTTP

✅

❌ No auto-browser

✅ Stable

Only for mcp-remote

Does not open browser for OAuth; must use mcp-remote

Windsurf

Streamable HTTP

✅

⚠️ Unreliable

✅ Stable

Only for mcp-remote

Uses serverUrl instead of url in config

Claude Desktop

STDIO only

✅ Via mcp-remote

❌ N/A

✅ Stable

Always

STDIO-only; all connections require mcp-remote. Restart required after config changes

Claude Web

Streamable HTTP

✅

⚠️ Inconsistent

N/A

Sometimes works, sometimes doesn't, even on Official MCP Servers.

ChatGPT Web

Streamable HTTP

✅

⚠️ Inconsistent

N/A

Requires Plus or higher; Business requires admin access. Still inconsistent.

Google Antigravity

STDIO only

✅ Via mcp-remote

❌ N/A

✅ Stable

Always

Requires mcp-remote

Kiro

STDIO only

✅ Via mcp-remote

❌ N/A

✅ Stable

Always

Requires mcp-remote

Headless / CI

Varies

✅

❌ Not possible

—

No browser available; token-based auth only

Legend: ✅ Works — ⚠️ Works sometimes / unreliable — ❌ Does not work or not applicable

Key takeaway: Token-based auth works everywhere. Native OAuth 2.1 is unreliable across the board — even clients that support it (VSCode, Windsurf) frequently fail with certain servers. mcp-remote is the most reliable way to use OAuth today, but it requires Node.js (v20+) and NPM. See the In-Depth Guide for why this is the case.

Headers Reference

All token-based configurations use the same headers. Replace the placeholder values with your actual Credentials (obtained via the Connectors Console or other sources).

Header

Required

Description

Authorization

Yes

Your User Token, prefixed with Bearer (e.g., Bearer eyJ...)

X-Integration

Target a specific integration when you have multiple

Important: Do not omit the Bearer prefix. Authorization: eyJ... will fail — it must be Authorization: Bearer eyJ....

About mcp-remote

Several clients below reference mcp-remote — a bridge that enables STDIO-only clients to connect to Streamable HTTP MCP servers, and also handles the OAuth 2.1 browser flow externally.

When to use it:

Your client only supports STDIO (e.g., Claude Desktop, Kiro)
Native OAuth 2.1 fails in your client (which is common)
You want the most reliable OAuth experience available today

Requirements: Node.js (v20+) and NPM must be installed. The command runs via npx.

VSCode

VSCode has native support for Streamable HTTP MCP servers.

Config location: Command palette (Ctrl+Shift+P / Cmd+Shift+P) → MCP: Open User Configuration → edit mcp.json.

Token-based

{
  "mcp": {
    "servers": {
      "gmail": {
        "type": "http",
        "url": "https://connectors.gdplabs.id/google_mail/mcp",
        "headers": {
          "Authorization": "Bearer eyJ..."
        }
      }
    }
  }
}

OAuth 2.1

Native OAuth may work but is unreliable. Try native first, fall back to mcp-remote.

Native

{
  "mcp": {
    "servers": {
      "gmail": {
        "type": "http",
        "url": "https://connectors.gdplabs.id/google_mail/mcp"
      }
    }
  }
}

Via mcp-remote (recommended fallback)

{
  "mcp": {
    "servers": {
      "gmail": {
        "type": "stdio",
        "command": "npx",
        "args": ["-y", "mcp-remote", "https://connectors.gdplabs.id/google_mail/mcp"]
      }
    }
  }
}

Cursor

Cursor supports Streamable HTTP natively for token-based auth. For OAuth, it does not open the browser automatically — use mcp-remote.

Config location: File → Preferences → Cursor Settings → Tools & MCP → New MCP Server.

Token-based

{
  "mcpServers": {
    "gmail": {
      "url": "https://connectors.gdplabs.id/google_mail/mcp",
      "headers": {
        "Authorization": "Bearer eyJ..."
      }
    }
  }
}

OAuth 2.1 (via mcp-remote)

{
  "mcpServers": {
    "gmail": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://connectors.gdplabs.id/google_mail/mcp"]
    }
  }
}

Windsurf

Windsurf has native support for both Streamable HTTP and OAuth 2.1, though OAuth may not work reliably with all servers.

Config location: File → Preferences → Windsurf Settings → Cascade → Open MCP Marketplace → click the gear icon.

Token-based

{
  "mcpServers": {
    "gmail": {
      "serverUrl": "https://connectors.gdplabs.id/google_mail/mcp",
      "headers": {
        "Authorization": "Bearer eyJ..."
      }
    }
  }
}

OAuth 2.1

Native:

{
  "mcpServers": {
    "gmail": {
      "serverUrl": "https://connectors.gdplabs.id/google_mail/mcp"
    }
  }
}

Via mcp-remote (recommended fallback):

{
  "mcpServers": {
    "gmail": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://connectors.gdplabs.id/google_mail/mcp"]
    }
  }
}

Claude Desktop

Claude Desktop only supports STDIO-based MCP servers. All connections require mcp-remote and therefore Node.js.

Config location: Settings → Developer → Edit Config → edit claude_desktop_config.json. Restart Claude Desktop after saving.

Token-based

{
  "mcpServers": {
    "gmail": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://connectors.gdplabs.id/google_mail/mcp",
        "--header",
        "Authorization: Bearer eyJ..."
      ]
    }
  }
}

To target a specific integration, add additional --header arguments:

{
  "mcpServers": {
    "gmail": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://connectors.gdplabs.id/google_mail/mcp",
        "--header",
        "Authorization: Bearer eyJ...",
        "--header",
        "X-Integration: user..."
      ]
    }
  }
}

OAuth 2.1 (via mcp-remote)

{
  "mcpServers": {
    "gmail": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://connectors.gdplabs.id/google_mail/mcp"]
    }
  }
}

After saving and restarting Claude Desktop, mcp-remote will open your browser to complete the OAuth authorization flow.

Programmatic Usage

You can connect to GL Connector MCP servers programmatically using our in-house MCP Client. See the Connector MCP Cookbook for examples and advanced patterns.

Tips

Trailing slash: If your client cannot connect, try adding a trailing slash to the MCP URL (e.g., https://connectors.gdplabs.id/google_mail/mcp/).
Available connectors: Swap the URL path to connect to different services. See the full list at https://connectors.glair.ai/mcps/list
OAuth not working? This is expected. Try mcp-remote first, then fall back to token-based auth. See the In-Depth Guide.
Restart your client after editing MCP configuration. Most clients require this to pick up changes.

PreviousIn-Depth Guide NextGL Connectors MCP Setup Guide

Last updated 29 days ago

Was this helpful?

hashtagClient Comparison Matrix

hashtagHeaders Reference

hashtagAbout mcp-remote

hashtagVSCode

hashtagToken-based

hashtagOAuth 2.1

hashtagNative

hashtagVia mcp-remote (recommended fallback)

hashtagCursor

hashtagToken-based

hashtagOAuth 2.1 (via mcp-remote)

hashtagWindsurf

hashtagToken-based

hashtagOAuth 2.1

hashtagClaude Desktop

hashtagToken-based

hashtagOAuth 2.1 (via mcp-remote)

hashtagProgrammatic Usage

hashtagTips

Client Comparison Matrix

Headers Reference

About mcp-remote

VSCode

Token-based

OAuth 2.1

Native

Via mcp-remote (recommended fallback)

Cursor

Token-based

OAuth 2.1 (via mcp-remote)

Windsurf

Token-based

OAuth 2.1

Claude Desktop

Token-based

OAuth 2.1 (via mcp-remote)

Programmatic Usage

Tips