← Back

Welcorp MCP Server Setup Guide

How to connect this MCP server to your AI assistant.

MCP server URL

https://mcp.welcorp.com/mcp

Authentication is OAuth 2.0, discovered automatically by the client — there's no API key or token to generate or paste. Your assistant will open a browser sign-in against your Welcorp account and ask you to approve access.

Claude

claude.ai (web) / Claude Desktop

  1. Customize → Connectors (or the "+" button next to the chat box → Connectors).
  2. Click + Add custom connector.
  3. Paste the server URL above.
  4. Leave "Advanced settings" (OAuth Client ID/Secret) blank — the server discovers OAuth automatically, so these aren't needed unless Welcorp specifically issued you pre-registered credentials.
  5. Click Add, then Connect — this opens a browser sign-in to approve access.

Claude Code (CLI)

claude mcp add --transport http welcorp https://mcp.welcorp.com/mcp

OAuth is triggered automatically on first connection attempt.

Gemini

gemini.google.com (consumer web app / Gemini Advanced)

Not supported — the consumer web chat has no way to add a custom remote MCP URL. It's limited to first-party Google Workspace extensions and curated partner connectors.

Gemini Enterprise / Google Cloud

  1. Google Cloud Console → Gemini Enterprise dashboard.
  2. Data stores → Create data store → Custom MCP Server.
  3. Enter the server URL above (Streamable HTTP transport).
  4. Authentication → OAuth 2.0. Gemini Enterprise may ask for a Client ID, Client Secret, Authorization URL, and Token URL to be entered explicitly rather than discovering them automatically — if so, contact support for these details.

Gemini CLI

{
  "mcpServers": {
    "welcorp": {
      "httpUrl": "https://mcp.welcorp.com/mcp",
      "timeout": 5000
    }
  }
}

Add this to your Gemini CLI config file. OAuth is triggered automatically on first use, prompting a browser sign-in.

Grok

grok.com (web) / Grok apps

  1. Connectors → New Connector → Custom.
  2. Enter a name (e.g. "Welcorp MCP Server") and paste the server URL above.
  3. Complete the OAuth browser sign-in and approve access.

Grok Build (CLI)

grok mcp add --transport http welcorp https://mcp.welcorp.com/mcp

OAuth triggers automatically on first use. (Config-file alternative: a [mcp_servers.welcorp] block with a url key in ~/.grok/config.toml.)

xAI API (developers)

Programmatic use via the SDK passes a Bearer token directly rather than going through the interactive OAuth flow above — relevant only if you're building against the API directly, not connecting a chat assistant.

Other clients

Most IDE/CLI-based MCP clients (Cursor, Windsurf, VS Code extensions such as GitHub Copilot or Cline, etc.) use a JSON config file with a similar shape:

{
  "mcpServers": {
    "welcorp": {
      "type": "http",
      "url": "https://mcp.welcorp.com/mcp"
    }
  }
}

The key name is sometimes transport instead of type, depending on the client. OAuth discovery happens automatically the same way once the client reads the URL. A client that only supports local/stdio MCP servers, not remote HTTP, won't be able to connect at all.

Need help? Contact Welcorp support.