ChipsAI MCP Server
MCP (Model Context Protocol) server for ChipsAI — manage chatbots, conversations, documents, and AI models from Claude Code, Claude Desktop, or any MCP client.
Requirements
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 ChipsAI dashboard.
| Variable | Description | Default |
|---|---|---|
CHIPSAI_API_KEY |
Your ChipsAI API key (recommended) | — |
CHIPSAI_API_URL |
API base URL | https://ai.chipsbuilder.com |
Legacy: username/password authentication
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 |
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) |
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 |
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?"
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
Metadata
Release files for chipsai-mcp 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| chipsai_mcp-1.1.0.tar.gz | 7.2 kB | Without provenance | Details for chipsai_mcp-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chipsai_mcp-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for chipsai_mcp-1.1.0-py3-none-any.whl |
Total release size: 22.3 kB
Release files / chipsai_mcp-1.1.0.tar.gz
| Download URL | chipsai_mcp-1.1.0.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4dded48ba61267203666791b42c93c33db87bd3e59f73ef38698145193c15905
|
|
BLAKE2b-256 checksum How to use checksums |
e6f3ce702203b47ff3b0b1d2e765e074c5e9b5477f584c73feac81891e69fc68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / chipsai_mcp-1.1.0-py3-none-any.whl
| Download URL | chipsai_mcp-1.1.0-py3-none-any.whl |
|---|---|
| Size | 15.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92a258d2199ce304f2db4fc3744e6ff91c5d11d7e1f74a3b93d612a598fe5a68
|
|
BLAKE2b-256 checksum How to use checksums |
835f8289424fb26cd79432d6db36690c9e7639820505952726abdc70b9cf3331
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for chipsai-mcp 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.