MCP server for ChipsAI — manage chatbots, conversations, and AI models
MCP server for ChipsAI — manage chatbots, conversations, and AI models. The chipsai mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
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.
Everything the assistant can do here goes through one of these:
Conversations — The Conversations tool exposed by this serverChat — The Chat tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 2 environment variables: CHIPSAI_API_KEY, CHIPSAI_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. ChipsAI's toolset — Conversations, Chat — is a fair guide to whether it matches your workflow. It is maintained by fgasparetto; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Conversations | The Conversations tool exposed by this server. |
| Chat | The Chat tool exposed by this server. |
{
"mcpServers": {
"chipsai": {
"command": "uvx",
"args": ["chipsai-mcp"],
"env": {
"CHIPSAI_API_KEY": "chipsai_your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CHIPSAI_API_KEY | Credential the server authenticates with. | Yes |
| CHIPSAI_API_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.