
ChipsAI MCP Server
io.github.fgasparetto由 GitHub 账号 fgasparetto 发布v1.0.1更新于 Oct 24, 2026
MCP server for ChipsAI — manage chatbots, conversations, and AI models
概览
让助手通过 ChipsAI API 管理 ChipsAI/ChipsBot 的聊天机器人、会话、RAG 设置、机器人路由和 AI 模型。
- 可以做什么
- 将 MCP 客户端连接到 ChipsAI 账户,助手可以列出、创建、更新和停用聊天机器人,并查看其分析数据。它还能处理会话和网页挂件会话历史、发送消息获取 AI 回复、把 PDF/DOC/DOCX 文档上传到机器人的知识库,并读取或调整每个机器人的 RAG 设置,如阈值、分块、HyDE、L2 注入和重排序。可以配置机器人之间的路由,助手也能查询积分余额和可用 AI 模型。
- 适用场景
- 适合在 ChipsAI 上运行聊天机器人,并希望通过 MCP 客户端而非控制台来管理机器人、知识库和路由的场景。也适合查看会话历史与分析数据,或用对话方式调整 RAG 参数。
- 运行要求
- 以 stdio 方式在本地运行;需要 Python 3.11+ 以及 uv 或 pip,并拥有 ChipsAI/ChipsBot 账户。认证使用 CHIPSAI_API_KEY(推荐)或旧版 CHIPSAI_USERNAME 与 CHIPSAI_PASSWORD;清单中还列出 CHIPSAI_EMAIL 和 CHIPSAI_PASSWORD。需要访问 ChipsAI API 的网络,CHIPSAI_API_URL 默认指向提供方的端点。
安装
在 SourceWeft 中
- 打开 控制台中的 ChipsAI MCP Server,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
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
来源:README.md,提交 3543d24
工具
0版本历史
1- v1.0.1最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分