# 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. <a href="https://build.chipp.ai/plans" target="_blank" rel="noopener noreferrer">Upgrade to Builder</a>

## 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:

<div>
  
  
  
  
  
  
</div>

## Quick Start

### 1. Add to Your MCP Client

Add the Chipp server to your configuration:

**Claude Code** (`~/.claude.json`):
```json
{
  "mcpServers": {
    "chipp": {
      "url": "https://build.chipp.ai/mcp",
      "transport": "streamable-http"
    }
  }
}
```

**Cursor** (Settings > MCP):
```json
{
  "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](/docs/guides/mcp/authentication#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

<div>
  
  
  
  
  
</div>

## Need Help?

- [Troubleshooting Guide](/docs/guides/mcp/authentication#troubleshooting)
- [Email support@chipp.ai](mailto:support@chipp.ai)
- [Join Discord](https://discord.gg/chipp) for community help