Chipp MCP Server

The Chipp MCP Server is a hosted Streamable HTTP MCP server for managing Chipp apps programmatically from MCP clients such as Claude Code, Cursor, and compatible custom clients.

Installation / Setup

No local package is installed for this server. Chipp MCP is hosted by Chipp and is added to an MCP client as a remote Streamable HTTP server.

Prerequisites:

• Chipp account at https://build.chipp.ai.
• Builder plan or higher; Free tier users do not have MCP access.
• MCP client that supports Streamable HTTP, such as Claude Code, Cursor, or another compatible client.
• OAuth 2.0 with PKCE support for interactive authorization, or a Chipp API key for automation.

Claude Code setup:

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

Add that server entry to ~/.claude.json, restart Claude Code, then trigger a Chipp tool call. Claude Code opens a browser for Chipp authorization and stores refreshed tokens after approval.

Cursor setup:

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

Alternatively, use Cursor Settings > MCP and add a server named chipp with URL https://build.chipp.ai/mcp and transport streamable-http.

Generic MCP client setup:

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

For non-interactive automation, configure the Authorization header with a bearer API key:

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

API keys are created in Chipp Settings > Developer > API Keys, are shown only once, and should be treated as secrets.

Connection

Use the hosted endpoint https://build.chipp.ai/mcp with transport streamable-http. OAuth discovery is available at https://build.chipp.ai/.well-known/oauth-authorization-server. The server uses JSON-RPC 2.0 over Streamable HTTP.

Authentication

The server supports OAuth 2.0 Authorization Code Flow with PKCE for interactive clients and API-key bearer authentication for automation. OAuth uses the build.chipp.ai authorization, token, dynamic registration, and revocation endpoints. PKCE method S256 is required. API keys use the chipp_sk_ prefix and are passed as an Authorization: Bearer ... header.

Capabilities

The tools reference documents broad Chipp platform management capabilities across apps, configuration, knowledge sources, analytics, tags, evaluations, custom actions, MCP integrations, deployments, consumers, workspaces, billing, prompt engineering, action collections, variables, heartbeat, agent links, database connections, and monetization.

Requirements and Limits

MCP access requires a Chipp account on the Builder plan or higher. Free tier users do not have MCP access. Rate limits are tier-based: Builder 30 requests/minute, Studio 60, Studio Pro 120, and Enterprise unlimited. Clients should respect Retry-After and X-RateLimit-* response headers.