Chipp MCP

आधिकारिक

Shopify ने ई-कॉमर्स के लिए जो किया, Chipp AI एजेंट्स के लिए वही करता है। अपने व्यवसाय के लिए AI एजेंट बनाएं, तैनात करें और मुद्रीकृत करें — किसी इंजीनियरिंग टीम की आवश्यकता नहीं।

chipp.ai पर देखेंइस MCP को आज़माएँप्रायोजित

Chipp MCP के साथ आप क्या कर सकते हैं?

List Chipp apps — Ask your assistant to retrieve all your Chipp applications in one conversation.
Create a new app — Instruct the assistant to build a customer support bot or other app, e.g., "Create a customer support bot called HelpDesk."
Manage knowledge bases — Have the assistant add URLs or files to an app's knowledge base, like "Add https://docs.example.com to my FAQ app's knowledge base."
Update prompts across apps — Direct the assistant to change system prompts or models (e.g., GPT-4o) across multiple applications at once.
Review analytics — Ask for conversation analytics or identify apps with low satisfaction scores from your dashboard data.
Run evaluations — Request automated evals on your bots, such as "Run evals on all my customer service bots."

दस्तावेज़

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

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

{
  "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