Chipp MCP
officialWhat Shopify did for ecommerce, Chipp does for AI agents. Build, deploy, and monetize AI agents for your business — no engineering team required.
What can you do with Chipp MCP?
- List and create apps — Ask your assistant to list all your Chipp apps or create a new one, such as a customer support bot named HelpDesk.
- Update system prompts in bulk — Request prompt changes across multiple apps at once, like switching every app to a different model.
- Add knowledge sources — Add URLs or files to an app's knowledge base, including bulk additions to an FAQ bot.
- Review conversation analytics — Ask for analytics over a time range or surface apps with low satisfaction scores.
- Run evaluations — Trigger evals on your bots, such as all customer service bots, from the same conversation.
- Connect via
core— Start with the lightweightcoreMCP (about 2,600 tokens) and add other Chipp MCPs as needed.
Documentation
Chipp MCP Server
Connect any MCP client to manage your Chipp apps programmatically
The Chipp MCP Server enables AI assistants like Claude Code, Cursor, and other Model Context Protocol (MCP) clients to read, create, and manage your Chipp applications programmatically.
Note: MCP server access requires a Builder plan or higher. Upgrade to Builder
Note: Two products, one URL. This page covers the Chipp MCP (tokens
chipp_sk_*/ OAuth). Use it to manage Chipp apps: system prompts, knowledge, custom actions, analytics. Is your org entitled (STUDIO_PRO, ENTERPRISE, or Chipp Executive), and has it connected the software factory under Settings → Alchemist Cloud? Then this same session already has the full software factory catalog too, tickets, database access, repo search, release control, billing, all of it, documented on the Software Factory Tickets MCP page. No separate key needed to reach any of it. A dedicatedalch_*credential is still useful for two narrower cases: an OAuth hosted connector (claude.ai, ChatGPT) that needs a URL rather than Chipp's own OAuth, or a tenant-wide key for headless automation that should not be tied to one person's login. Both paths reachhttps://build.chipp.ai/mcp; the server routes by token type. The software factory server's own URL,https://build.chipp.ai/alchemist-api/api/mcp, still works too.
Why Use the MCP Server?
| Use Case | Without MCP | With MCP |
|---|---|---|
| Create 10 apps | Click through UI 10 times | One conversation with your AI |
| Update prompts across apps | Open each app, edit, save | "Update all my apps to use GPT-4o" |
| Bulk add knowledge sources | Upload files one by one | "Add these 50 URLs to my FAQ bot" |
| Monitor analytics | Check dashboard daily | "Show me apps with low satisfaction" |
| Run evaluations | Manual testing | "Run evals on all my customer service bots" |
Comparison: MCP vs API vs Pro Actions
| Feature | MCP Server | REST API | Pro Actions |
|---|---|---|---|
| Best for | AI-assisted workflows | Custom integrations | Connecting external services |
| Authentication | OAuth 2.0 + PKCE, or API Keys | API Keys | OAuth per service |
| Rate limits | Tier-based | Tier-based | Per service limits |
| Scope | Full Chipp platform | Full Chipp platform | External services only |
| Typical user | Developers using AI tools | Backend developers | No-code builders |
What You Can Do
Once connected, your AI assistant can manage:
Quick Start
Tip: Connect only what you need. Chipp is split into small MCPs, one per area (agents, knowledge, analytics, tickets, releases, and more). Every tool an MCP lists is sent to your AI model with each message: the full server is about 157,000 tokens per message,
coreis about 2,600. Start withhttps://mcp.chipp.ai/mcp/coreand add the others you need. See Chipp MCPs for the list.
1. Add to Your MCP Client
The setup path depends on which Claude product you use:
Claude app or Claude Cowork (most users): Use the built-in connector UI. See Connect from Claude App or Claude Cowork for a step-by-step walkthrough.
Claude Code (terminal, edit ~/.claude.json), with core plus the MCPs you need:
{
"mcpServers": {
"chipp-core": {
"type": "http",
"url": "https://mcp.chipp.ai/mcp/core"
},
"chipp-apps": {
"type": "http",
"url": "https://mcp.chipp.ai/mcp/apps"
}
}
}
Or everything in one server (about 157,000 tokens per message):
{
"mcpServers": {
"chipp": {
"type": "http",
"url": "https://build.chipp.ai/mcp"
}
}
}
Cursor (Settings > MCP):
{
"chipp": {
"url": "https://build.chipp.ai/mcp",
"transport": "streamable-http"
}
}
2. Authenticate
When you first use a Chipp tool, your client will open a browser window. Log in with your Chipp account to authorize access.
Alternatively, you can use an API key for non-interactive authentication. See API Keys.
3. Start Building
"List all my Chipp apps"
"Create a customer support bot called HelpDesk"
"Add https://docs.example.com to my FAQ app's knowledge base"
"Show me conversation analytics for the past week"
Server Details
| Property | Value |
|---|---|
| Server URLs | https://mcp.chipp.ai/mcp/<id>, one per Chipp MCP (recommended) |
| Everything | https://build.chipp.ai/mcp or https://mcp.chipp.ai/mcp (about 157,000 tokens per message) |
| Discovery | https://build.chipp.ai/.well-known/oauth-authorization-server |
| Protocol | JSON-RPC 2.0 over Streamable HTTP |
| Authentication | OAuth 2.0 with PKCE, or API Keys |
Guides
Need Help?
- Troubleshooting Guide
- Email support@chipp.ai
- Join Discord for community help