MCP server for ChipsAI — manage chatbots, conversations, and AI models
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.
No installation needed with uv:
uv run --script server.py
Or install manually:
pip install "mcp[cli]" httpx
python server.py
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 |
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 |
Add to your project's .mcp.json:
{
"mcpServers": {
"chipsai": {
"command": "uvx",
"args": ["chipsai-mcp"],
"env": {
"CHIPSAI_API_KEY": "chipsai_your_api_key_here"
}
}
}
}
Add to claude_desktop_config.json:
{
"mcpServers": {
"chipsai": {
"command": "uvx",
"args": ["chipsai-mcp"],
"env": {
"CHIPSAI_API_KEY": "chipsai_your_api_key_here"
}
}
}
}
| 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 |
| Tool | Description |
|---|---|
upload_document | Upload PDF/DOC/DOCX to a chatbot's knowledge base (LlamaParse) |
| 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 |
| Tool | Description |
|---|---|
list_conversation_history | List widget conversation sessions (paginated, filter by chatbot) |
get_session_messages | Get all messages from a widget conversation session |
| Tool | Description |
|---|---|
send_message | Send a message and get AI response (auto-creates conversation) |
| 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 |
| 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.) |
| Tool | Description |
|---|---|
get_user_plan | Get credit balance, unlimited status, usage stats |
list_ai_models | List available AI models by provider with credit costs |
ChipsBot supports a full Retrieval-Augmented Generation pipeline configurable per-bot:
jina-reranker-v2-base-multilingual) applied after cosine retrievalchar (fixed size), paragraph (semantic \n\n split), sentence (.!? split)Use get_rag_config / update_rag_config to tune all parameters per-bot.
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.
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).
Once configured, use natural language in Claude:
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.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx chipsai-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-fgasparetto-chipsai-mcp": {
"command": "uvx",
"args": [
"chipsai-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencechipsai-mcppypiChipsAI MCP Server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.