# Chipp MCP Server Overview Connect Claude Code or any MCP client to your Chipp apps for AI-powered app building --- The Chipp MCP Server lets you connect Claude Code, Cursor, or any Model Context Protocol (MCP) client directly to your Chipp apps, so an AI assistant can read, create, and manage your applications programmatically. > **Note:** This page has moved. The full, always-current documentation lives in the [MCP Server hub](/docs/guides/mcp/). ## Quick Start Add Chipp to Claude Code from your terminal: ```bash claude mcp add --transport http chipp https://build.chipp.ai/mcp ``` Or add it to your project's `.mcp.json`: ```json { "mcpServers": { "chipp": { "type": "http", "url": "https://build.chipp.ai/mcp" } } } ``` Then authenticate via the OAuth prompt and start building: "List all my Chipp apps." ## Documentation - [MCP Server Overview](/docs/guides/mcp/) - what it is, why to use it, capability tour - [Setup & Installation](/docs/guides/mcp/setup) - Claude Code, Cursor, and generic clients - [Authentication](/docs/guides/mcp/authentication) - OAuth 2.0 + PKCE, API keys (`chipp_sk_*`), scopes - [Tools Reference](/docs/guides/mcp/tools-reference) - every available tool, by category - [Common Workflows](/docs/guides/mcp/workflows) - step-by-step examples - [Rate Limits](/docs/guides/mcp/rate-limits) - tier-based limits and optimization tips ## Related - [Software Factory Tickets MCP](/docs/guides/alchemist-mcp-server) - the full software factory catalog: tickets, database access, repo search, release control, billing. Is your org entitled and connected? Then this same Chipp MCP session already has all of it. No `alch_` key needed, that credential is only for OAuth hosted connectors or tenant-wide headless automation. - [Builder API](/docs/builder-api/overview) - REST access with per-app keys - [Building Custom MCP Servers](/docs/guides/building-custom-mcp-servers) - create your own MCP integrations