Connect border.bot to your AI tools

Claude

By Anthropic. Free, Pro, Max, Team and Enterprise (Free is limited to one custom connector). On Team and Enterprise an Owner adds it for the organization.

1. Open Customize › Connectors (claude.ai/customize/connectors), click “+ Add”, then “Add custom connector”.
2. Enter border.bot as the name and https://api.border.bot/mcp as the remote MCP server URL, then click “Continue”.
3. Review the authentication settings Claude detected and click “Continue”; under Authentication choose “Sign in now” and under OAuth client “Use Claude’s published identity (Recommended)”, then click “Add”.
4. Sign in to border.bot and approve access in the window that opens.
5. In a chat, open “+” › “Connectors” and switch border.bot on.

One connector covers claude.ai, Claude Desktop, Cowork and the mobile apps. Claude connects from Anthropic’s cloud, so the URL must be publicly reachable. Team/Enterprise: an Owner adds it under Organization settings › Connectors (“Add” › “Custom” › “Web”), then each member clicks “Connect” in Customize › Connectors.

ChatGPT

By OpenAI. ChatGPT on the web. OpenAI’s help center lists full MCP (read and write tools) for Business, Enterprise and Edu (beta) and read/fetch-only custom MCP for Pro in developer mode; workspace admins control who may create plugins with MCP servers.

1. Go to ChatGPT Plugins (chatgpt.com/plugins), select the plus button, then “Add custom MCP server”.
2. Enter border.bot as the name and, under “Connection”, https://api.border.bot/mcp as the “Server URL”.
3. Choose “OAuth” for authentication, review the risk warning, select “I understand and want to continue”, then “Create as a plugin”.
4. Open the new plugin in your personal plugins, install it with the plus button and sign in to border.bot when asked.
5. In a new chat, type @ and select border.bot.

Not available in the mobile apps. ChatGPT supports Client ID Metadata Documents and Dynamic Client Registration. Write tools ask for confirmation unless marked read-only. Workspaces still on the older flow create it under Settings › Apps › Create with developer mode on.

Gemini

By Google. Personal Google Accounts only (not work or school), 18+ in the US, with Keep Activity on; English only. Added on the web, then usable in the web and mobile apps.

1. On a computer, go to gemini.google.com and click Settings › “Connected Apps” at the bottom.
2. Under “Custom apps”, click “Add a custom app” and enter https://api.border.bot/mcp as the MCP server URL.
3. Click “Next” and follow the on-screen instructions to sign in to border.bot.
4. In a chat, enter @ and select the app to make sure Gemini uses it.

Gemini registers itself with Dynamic Client Registration, so no client credentials are needed. Write actions always need manual confirmation.

Perplexity

Pro, Max and Enterprise. Enterprise members can add their own only when an admin allows custom connectors.

1. Go to Account settings › Connectors, click “+ Custom connector” in the top-right corner and select “Remote”.
2. Name: border.bot; MCP Server URL: https://api.border.bot/mcp; Authentication: “OAuth”; Transport: “Streamable HTTP”.
3. Check the acknowledgement box and click “Add”.
4. Click the border.bot connector card to start the sign-in and enable it.

Perplexity discovers border.bot’s OAuth endpoints and registers itself dynamically, so no client ID or secret is needed. Enterprise admins can add it for everyone under Enterprise settings › Permissions › Connectors permissions.

Vibe Work (formerly Le Chat)

By Mistral AI. Administrators only: on Free, Pro and Student plans the account owner is the administrator.

1. In Vibe Work (chat.mistral.ai), open the “Connectors” page from the sidebar.
2. Click “+ Add Connector” and switch to the “Custom MCP Connector” tab.
3. Connector name: borderbot; Server URL: https://api.border.bot/mcp; then click “Connect”.
4. Complete the OAuth consent flow when prompted.

Formerly Le Chat. The authentication method (OAuth 2.1 with dynamic client registration) is detected automatically. Under “Connectors” › “My Connectors” › “Functions” you can mark read-only tools “Always allow”.

Raycast

Raycast Pro.

1. Open the “Install MCP Server” command in Raycast.
2. Name: border.bot; Transport: “HTTP”; URL: https://api.border.bot/mcp; OAuth Type: “Dynamic”.
3. Press “Install MCP Server” (⌘↵), then select “Sign In” to authorize border.bot.
4. In AI Chat or Quick AI, type @ and the server’s name to use it.

Works on desktop and iOS (HTTP servers only on iOS). The “Logout Server” action in “Manage MCP Servers” clears saved tokens.

LM Studio

By Element Labs.

1. Click “Add to LM Studio”, or open the “Program” tab in the right-hand sidebar, click “Install” › “Edit mcp.json” and add the config snippet.
2. LM Studio opens border.bot’s authorization page in your browser; approve access.
3. border.bot’s tools are then available to your models in chat.

{
  "mcpServers": {
    "borderbot": {
      "url": "https://api.border.bot/mcp"
    }
  }
}

OAuth sign-in for MCP servers needs LM Studio 0.4.10 or later. Install-link format: lmstudio.ai/docs/app/mcp/deeplink.

Claude Code

By Anthropic.

1. Run claude mcp add --transport http --scope user borderbot https://api.border.bot/mcp.
2. Start Claude Code, run /mcp, select borderbot and follow the steps in your browser to log in (or run claude mcp login borderbot from your shell).
3. Run /mcp again to confirm borderbot is connected.

claude mcp add --transport http --scope user borderbot https://api.border.bot/mcp

{
  "mcpServers": {
    "borderbot": {
      "type": "http",
      "url": "https://api.border.bot/mcp"
    }
  }
}

--scope user makes border.bot available in every project; the .mcp.json snippet is for sharing it with a team via a repository. Claude Code discovers OAuth and border.bot’s Client ID Metadata Document support automatically and refreshes tokens itself. If you added border.bot as a connector on claude.ai and log in to Claude Code with that account, it already appears in /mcp.

Codex

By OpenAI.

1. CLI: run codex mcp add borderbot --url https://api.border.bot/mcp, then codex mcp login borderbot and sign in to border.bot in your browser.
2. IDE extension: open the gear menu › “MCP servers” › “Add server”, enter borderbot, choose “Streamable HTTP”, paste https://api.border.bot/mcp, save and select “Restart extension”, then “Authenticate”.
3. ChatGPT desktop app: “Settings” › “MCP servers” › “Add server” with the same values, save and select “Restart”, then “Authenticate”.
4. Type /mcp to see the connected servers.

codex mcp add borderbot --url https://api.border.bot/mcp

[mcp_servers.borderbot]
url = "https://api.border.bot/mcp"

The Codex CLI, IDE extension and ChatGPT desktop app share ~/.codex/config.toml, so adding border.bot once covers all three. Codex uses a Client ID Metadata Document when the authorization server advertises it and otherwise Dynamic Client Registration, with a loopback callback on 127.0.0.1.

Gemini CLI

By Google.

1. Run gemini mcp add --transport http --scope user borderbot https://api.border.bot/mcp.
2. Start gemini and run /mcp auth borderbot; sign in to border.bot in the browser window that opens.
3. Run /mcp list to check that borderbot is connected.

gemini mcp add --transport http --scope user borderbot https://api.border.bot/mcp

{
  "mcpServers": {
    "borderbot": {
      "httpUrl": "https://api.border.bot/mcp"
    }
  }
}

Use httpUrl for Streamable HTTP. url means SSE in Gemini CLI. OAuth needs a local browser and a localhost callback, so it doesn’t work in headless or SSH sessions without forwarding.

GitHub Copilot CLI

By GitHub. All Copilot plans. With Copilot from an organization, the Copilot CLI policy must be enabled, and MCP allowlist policies apply.

1. Run copilot mcp add --transport http borderbot https://api.border.bot/mcp, or in interactive mode enter /mcp add, pick “HTTP or SSE”, paste the URL and press Ctrl+S.
2. If borderbot shows needs-auth, run /mcp auth borderbot and sign in to border.bot in your browser.
3. Run /mcp show borderbot to see its status and tools.

copilot mcp add --transport http borderbot https://api.border.bot/mcp

{
  "mcpServers": {
    "borderbot": {
      "type": "http",
      "url": "https://api.border.bot/mcp",
      "tools": [
        "*"
      ]
    }
  }
}

Copilot CLI registers itself with Dynamic Client Registration. ~/.copilot/mcp-config.json is also read by Visual Studio Code.

OpenCode

By Anomaly.

1. Add border.bot under "mcp" in ~/.config/opencode/opencode.json using the config snippet (or run opencode mcp add and choose a remote server).
2. Run opencode mcp auth borderbot and authorize in your browser. OpenCode also prompts the first time you use it.
3. Run opencode mcp list to check its connection and auth status.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "borderbot": {
      "type": "remote",
      "url": "https://api.border.bot/mcp"
    }
  }
}

OpenCode uses Dynamic Client Registration automatically; no client ID is needed.

Warp

1. Open Settings › Agents › MCP servers (or run “Open MCP Servers” from the Command Palette) and click “+ Add”.
2. Paste the config snippet and save.
3. Start borderbot; Warp opens a browser to sign in to border.bot the first time.

{
  "mcpServers": {
    "borderbot": {
      "url": "https://api.border.bot/mcp"
    }
  }
}

Servers in ~/.warp/.mcp.json start automatically and show an authentication modal on first spawn. Credentials stay on the device, so sign in again on a new machine.

Junie CLI

By JetBrains.

1. Add the config snippet to ~/.junie/mcp/mcp.json, or run /mcp, press Ctrl+A to add a server with the MCP Installation Assistant, and choose “User scope” and “Remote”.
2. border.bot shows the “Authorization required” status: select it, choose “Authorize” and log in on the border.bot page that opens.
3. Check that its status changes to “Active”.

{
  "mcpServers": {
    "borderbot": {
      "url": "https://api.border.bot/mcp"
    }
  }
}

Junie in JetBrains IDEs reads the same ~/.junie/mcp/mcp.json, but JetBrains documents OAuth sign-in only for Junie CLI. JetBrains AI Assistant chat can’t sign in to OAuth MCP servers yet.

Amp

1. Run amp mcp add borderbot https://api.border.bot/mcp (saved to amp.mcpServers in ~/.config/amp/settings.json).
2. Start the Amp TUI (amp); it opens your browser to sign in to border.bot automatically.
3. To use border.bot from every Amp client, including orbs, store it on ampcode.com instead: amp mcp remote --personal add borderbot https://api.border.bot/mcp --auth oauth, then amp mcp remote --personal login borderbot.

amp mcp add borderbot https://api.border.bot/mcp

{
  "amp.mcpServers": {
    "borderbot": {
      "url": "https://api.border.bot/mcp"
    }
  }
}

Local sign-in relies on Dynamic Client Registration. Browser OAuth isn’t available inside orbs, so use the remote definition there.

goose

By Agentic AI Foundation.

1. Click “Add to goose”, or run goose configure › “Add Extension” › “Remote Extension (Streamable HTTP)” and enter borderbot and https://api.border.bot/mcp.
2. In goose Desktop you can also use the sidebar › “Extensions” › “Add custom extension”.
3. Sign in to border.bot in your browser when goose asks; it registers itself automatically (Client ID Metadata Document or Dynamic Client Registration).

extensions:
  borderbot:
    name: borderbot
    type: streamable_http
    uri: "https://api.border.bot/mcp"
    enabled: true
    timeout: 300

Qwen Code

By Alibaba Cloud.

1. Run qwen mcp add --scope user --transport http borderbot https://api.border.bot/mcp.
2. Start qwen, enter /mcp and authenticate borderbot; sign in to border.bot in your browser.
3. Ask the model to use border.bot (restart Qwen Code first if it was already running).

qwen mcp add --scope user --transport http borderbot https://api.border.bot/mcp

{
  "mcpServers": {
    "borderbot": {
      "httpUrl": "https://api.border.bot/mcp"
    }
  }
}

OAuth endpoints are discovered and the client registers dynamically. The callback is http://localhost:7777/oauth/callback, so sign-in needs a local browser.

Kimi Code CLI

By Moonshot AI.

1. Run kimi mcp add --transport http --auth oauth borderbot https://api.border.bot/mcp.
2. Run kimi mcp auth borderbot and complete the OAuth flow in your browser.
3. Run kimi mcp test borderbot (or /mcp inside Kimi Code CLI) to check the connection.

kimi mcp add --transport http --auth oauth borderbot https://api.border.bot/mcp

Servers are saved to ~/.kimi/mcp.json; OAuth tokens are kept in ~/.kimi/mcp-oauth/.