Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here
ChipsAI MCP Server logo

ChipsAI MCP Server

fgasparetto/chipsai-mcp
0 starsv1.0.1STDIORegistry activeMITUpdated 2026-04-29Community

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

claude mcp add chipsai -- uvx chipsai-mcp

Summary

Enables managing ChipsBot chatbots, conversations, documents, RAG configuration, bot-to-bot routing, and AI models through natural language.

Connect from your MCP client

One-click install

Add this server to your editor with a single click. Fill in any required credentials afterward.

Claude Code

Run this once and Claude Code registers the server for you:

claude mcp add chipsai -- uvx chipsai-mcp

Claude Desktop

Add this to claude_desktop_config.json under Settings → Developer → Edit Config:

{
  "mcpServers": {
    "chipsai": {
      "command": "uvx",
      "args": [
        "chipsai-mcp"
      ],
      "env": {
        "CHIPSAI_EMAIL": "<CHIPSAI_EMAIL>",
        "CHIPSAI_PASSWORD": "<CHIPSAI_PASSWORD>"
      }
    }
  }
}

Cursor

Add this to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

{
  "mcpServers": {
    "chipsai": {
      "command": "uvx",
      "args": [
        "chipsai-mcp"
      ],
      "env": {
        "CHIPSAI_EMAIL": "<CHIPSAI_EMAIL>",
        "CHIPSAI_PASSWORD": "<CHIPSAI_PASSWORD>"
      }
    }
  }
}

Cline and other MCP clients

Most MCP clients accept the standard mcpServers JSON block:

{
  "mcpServers": {
    "chipsai": {
      "command": "uvx",
      "args": [
        "chipsai-mcp"
      ],
      "env": {
        "CHIPSAI_EMAIL": "<CHIPSAI_EMAIL>",
        "CHIPSAI_PASSWORD": "<CHIPSAI_PASSWORD>"
      }
    }
  }
}

Codex CLI

Register the server with OpenAI's Codex CLI — run this once, or add the equivalent block to ~/.codex/config.toml:

codex mcp add chipsai --env CHIPSAI_EMAIL=<CHIPSAI_EMAIL> --env CHIPSAI_PASSWORD=<CHIPSAI_PASSWORD> -- uvx chipsai-mcp

# or add to ~/.codex/config.toml:
[mcp_servers.chipsai]
command = "uvx"
args = ["chipsai-mcp"]
[mcp_servers.chipsai.env]
CHIPSAI_EMAIL = "<CHIPSAI_EMAIL>"
CHIPSAI_PASSWORD = "<CHIPSAI_PASSWORD>"

OpenClaw

OpenClaw reads MCP servers from the mcp.servers section of ~/.openclaw/openclaw.json (managed via `openclaw mcp add` or the mcporter skill):

{
  "mcp": {
    "servers": {
      "chipsai": {
        "command": "uvx",
        "args": [
          "chipsai-mcp"
        ],
        "env": {
          "CHIPSAI_EMAIL": "<CHIPSAI_EMAIL>",
          "CHIPSAI_PASSWORD": "<CHIPSAI_PASSWORD>"
        }
      }
    }
  }
}

Replace the <PLACEHOLDER> values with your own credentials — see the configuration table below.

Configuration

ChipsAI MCP Server reads the following environment variables:

VariableRequired
CHIPSAI_EMAILRequired
CHIPSAI_PASSWORDRequired

README.md

<!-- mcp-name: io.github.fgasparetto/chipsai-mcp -->

ChipsAI MCP Server

MCP (Model Context Protocol) server for ChipsBot — manage chatbots, conversations, documents, bot-to-bot routing, RAG configuration, and AI models from Claude Code, Claude Desktop, or any MCP client.

Requirements

  • Python 3.11+
  • uv (recommended) or pip
  • A ChipsBot account (sign up)

Quick Start

No installation needed with uv:

uv run --script server.py

Or install manually:

pip install "mcp[cli]" httpx
python server.py

Configuration

The server uses environment variables for authentication. API key is the recommended method — generate one from your ChipsBot dashboard.

| Variable | Description | Default | |----------|-------------|---------| | CHIPSAI_API_KEY | Your ChipsAI API key (recommended) | — | | CHIPSAI_API_URL | API base URL | https://ai.chipsbuilder.com |

<details> <summary>Legacy: username/password authentication</summary>

If you don't have an API key, you can use username/password instead:

| Variable | Description | |----------|-------------| | CHIPSAI_USERNAME | Your ChipsAI username | | CHIPSAI_PASSWORD | Your ChipsAI password |

</details>

Claude Code

Add to your project's .mcp.json:

{
  "mcpServers": {
    "chipsai": {
      "command": "uvx",
      "args": ["chipsai-mcp"],
      "env": {
        "CHIPSAI_API_KEY": "chipsai_your_api_key_here"
      }
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "chipsai": {
      "command": "uvx",
      "args": ["chipsai-mcp"],
      "env": {
        "CHIPSAI_API_KEY": "chipsai_your_api_key_here"
      }
    }
  }
}

Available Tools

Chatbot Management

| Tool | Description | |------|-------------| | list_chatbots | List all chatbots for the authenticated user | | get_chatbot | Get full chatbot details (prompt, model, colors, etc.) | | create_chatbot | Create a new chatbot (returns embed script tag) | | update_chatbot | Update chatbot fields (name, prompt, model, theme, colors, etc.) | | delete_chatbot | Soft-delete (deactivate) a chatbot | | get_chatbot_config | Get public widget configuration | | get_chatbot_analytics | Get analytics: messages, sessions, daily stats, devices, countries |

Documents (RAG)

| Tool | Description | |------|-------------| | upload_document | Upload PDF/DOC/DOCX to a chatbot's knowledge base (LlamaParse) |

Conversations

| Tool | Description | |------|-------------| | list_conversations | List conversations, optionally filtered by chatbot | | create_conversation | Create a new conversation | | get_conversation | Get conversation details | | update_conversation | Update conversation title | | delete_conversation | Delete a conversation and all messages | | get_conversation_messages | Get all messages from a conversation |

Widget History

| Tool | Description | |------|-------------| | list_conversation_history | List widget conversation sessions (paginated, filter by chatbot) | | get_session_messages | Get all messages from a widget conversation session |

Chat

| Tool | Description | |------|-------------| | send_message | Send a message and get AI response (auto-creates conversation) |

Bot-to-Bot Connections

| Tool | Description | |------|-------------| | connect_bot | Connect a specialist bot to an orchestrator bot (role-based routing) | | list_bot_connections | List all specialist bots connected to an orchestrator | | update_bot_connection | Update role, label, description, or active status of a connection | | disconnect_bot | Remove a bot-to-bot connection |

RAG Configuration

| Tool | Description | |------|-------------| | get_rag_config | Get RAG config: threshold, chunk settings, HyDE, L2, reranker, system instructions | | update_rag_config | Update RAG config (threshold, chunk_size, chunk_strategy, HyDE, L2, reranker, etc.) |

User & Models

| Tool | Description | |------|-------------| | get_user_plan | Get credit balance, unlimited status, usage stats | | list_ai_models | List available AI models by provider with credit costs |

RAG Pipeline

ChipsBot supports a full Retrieval-Augmented Generation pipeline configurable per-bot:

  • Semantic routing (L1): pgvector + Jina Embeddings v3 — routes queries to the best specialist based on cosine similarity (HNSW index)
  • HyDE: for sparse/short queries, generates a hypothetical answer with Haiku and re-embeds it for better retrieval
  • Chunk injection (L2): at response time, injects only the top-K relevant KB chunks instead of the full prompt — reduces token usage, improves quality
  • Reranking: optional Jina cross-encoder reranker (jina-reranker-v2-base-multilingual) applied after cosine retrieval
  • Chunking strategies: char (fixed size), paragraph (semantic \n\n split), sentence (.!? split)
  • Document upload: PDF/DOC/DOCX parsed via LlamaParse, extracted text stored as KB

Use get_rag_config / update_rag_config to tune all parameters per-bot.

Bot-to-Bot Routing

An orchestrator bot can route questions to specialist bots based on role/description. The orchestrator detects [ROUTE:uuid] tags in its own response and delegates to the matching specialist, passing recent chat history as context.

Use connect_bot to link specialists to an orchestrator, list_bot_connections to inspect the routing table, and update_bot_connection to adjust roles or toggle connections on/off.

Credit System

ChipsAI uses a credit-based pricing model:

| Tier | Credits/msg | Models | |------|-------------|--------| | Free | 0 | Llama 4 Scout, Llama 3.3 70B, Llama 3.1 8B (Groq) | | Economy | 0.5 | Mistral Nemo, DeepSeek Chat | | Standard | 1.0 | GPT-4o-mini, Gemini 2.5 Flash, Mistral Small, Claude Haiku 4.5 | | Premium | 2.0 | GPT-4o, Mistral Large, DeepSeek Reasoner | | Top | 3.0 | GPT-4.1, Claude Sonnet 4.6, Gemini 2.5 Pro |

Credit packages: 150 credits for €5 | 700 for €20 | 2000 for €50. Credits never expire. Bring your own API key to use any model for free (no credits consumed).

Usage Examples

Once configured, use natural language in Claude:

  • "List my chatbots"
  • "Create a chatbot called Support Bot"
  • "Upload the product catalog PDF to my chatbot"
  • "Send a test message to my chatbot"
  • "Show analytics for the last 7 days"
  • "Change the chatbot model to Claude Sonnet 4.6"
  • "What's my credit balance?"
  • "What AI models are available?"
  • "Connect the billing bot as a specialist of my main orchestrator"
  • "List all specialist bots connected to my orchestrator"
  • "Show the RAG config for my chatbot"
  • "Set the RAG threshold to 0.5 and enable reranking"
  • "Enable L2 chunk injection with top_k=5"

Authentication

API Key (recommended): Set CHIPSAI_API_KEY with a key generated from your dashboard. The key is sent as a Bearer token — no token management needed.

JWT (legacy): If using username/password, tokens are obtained via JWT and refreshed transparently.

License

MIT

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Vector & Memory servers.