Chipp MCP

official

What Shopify did for ecommerce, Chipp does for AI agents. Build, deploy, and monetize AI agents for your business — no engineering team required.

View on chipp.aiTry this MCPSponsored

What can you do with Chipp MCP?

List all your Chipp apps — Ask your assistant to retrieve and display every app in your account using list_apps.
Create a new Chipp app — Have your AI build a complete app (e.g., a support bot) by specifying a name and configuration via create_app.
Update system prompts across apps — Instruct your assistant to modify the core prompt for one or multiple apps with update_app.
Add knowledge sources to an app — Provide URLs or files and let your AI attach them to a specific app’s knowledge base using add_knowledge.
Retrieve conversation analytics — Ask for satisfaction metrics or usage stats for a given time period through get_analytics.

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) for managing Chipp apps -- system prompts, knowledge, custom actions, analytics. If you want to drive Alchemist Cloud project tickets (dispatch tickets, list status, reply to paused agents, read production errors, query your app's database), see the Alchemist Cloud Tickets MCP -- a separate tool surface using alch_* tokens. Both are reachable at https://build.chipp.ai/mcp: the server routes by token type. (The Alchemist server's dedicated URL, https://build.chipp.ai/alchemist-api/api/mcp, also remains fully supported.)

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

1. Add to Your MCP Client

Add the Chipp server to your configuration:

Claude Code (~/.claude.json):

{
  "mcpServers": {
    "chipp": {
      "url": "https://build.chipp.ai/mcp",
      "transport": "streamable-http"
    }
  }
}

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 URL	`https://build.chipp.ai/mcp`
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