
ChipsAI MCP Server
io.github.fgasparettoPublished by GitHub account fgasparettov1.0.1Updated Nov 10, 2026
MCP server for ChipsAI — manage chatbots, conversations, and AI models
Overview
Lets an assistant manage ChipsAI/ChipsBot chatbots, conversations, RAG settings, bot routing, and AI models through the ChipsAI API.
- What you can do
- Connects an MCP client to a ChipsAI account so the assistant can list, create, update, and deactivate chatbots, and read their analytics. It also handles conversations and widget session history, sends messages to get AI replies, uploads PDF/DOC/DOCX documents into a bot's knowledge base, and reads or tunes per-bot RAG settings such as threshold, chunking, HyDE, L2 injection, and reranking. Bot-to-bot routing can be configured, and the assistant can check credit balance and available AI models.
- When to use it
- Useful when you run chatbots on ChipsAI and want to manage them, their knowledge bases, and their routing from an MCP client instead of the dashboard. Also suited to inspecting conversation history and analytics, or tuning RAG parameters conversationally.
- Requirements
- Runs locally over stdio; needs Python 3.11+ and uv or pip, plus a ChipsAI/ChipsBot account. Authentication uses CHIPSAI_API_KEY (recommended) or the legacy CHIPSAI_USERNAME and CHIPSAI_PASSWORD; the manifest also lists CHIPSAI_EMAIL and CHIPSAI_PASSWORD. Network access to the ChipsAI API is required, with CHIPSAI_API_URL defaulting to the provider's endpoint.
Installation
In SourceWeft
- Open ChipsAI MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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
Quick Start
No installation needed with uv:
Or install manually:
Configuration
The server uses environment variables for authentication. API key is the recommended method — generate one from your ChipsBot dashboard.
Legacy: username/password authentication
If you don't have an API key, you can use username/password instead:
Claude Code
Add to your project's .mcp.json:
Claude Desktop
Add to claude_desktop_config.json:
Available Tools
Chatbot Management
Documents (RAG)
Conversations
Widget History
Chat
Bot-to-Bot Connections
RAG Configuration
User & Models
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\nsplit),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:
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
Source: README.md at commit 3543d24
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts