ChatbotX MCP Server

What the code does

We read the source, 23 h ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

# COPY --from=pre /app/.env .env

# Build-time placeholders. `next build` evaluates module-level code (better-auth
# is instantiated when route/instrumentation modules load), so without these the
# build logs a "Base URL could not be determined" warning and falls back to
# better…

    <script
      async
      crossorigin="anonymous"
      onload="window.csmChatWidget?.init({
        webchatId: 'wdd2wgu9vl8qlylq83wggci9',
        workspaceId: 'fhrohnnmd3337cbggfae8vcc',
        brandColor: '##007bff',
        hideHeader: false,
        showLogo: false,
   …

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

claude mcp add mcp --transport http https://app.chatbotx.io/mcp/messages

https://app.chatbotx.io/mcp/messages

[mcp_servers.mcp]
url = "https://app.chatbotx.io/mcp/messages"

{
  "mcpServers": {
    "mcp": {
      "url": "https://app.chatbotx.io/mcp/messages"
    }
  }
}

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://app.chatbotx.io/mcp/messages"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Endpoints