Next liveBuild Your Chief of Staff · OnlineSave your seat →
Developer Platform

Chipp MCPs (pick only what you need)

The Chipp MCP is split into small MCPs, one per area. Connect core plus only the ones you need, so your AI assistant stays fast and cheap.

|View as Markdown
1 min read
#mcp#sub-mcp#claude#claude-code#chatgpt#connector#tokens

Every tool an MCP server lists is sent to your AI model with every message. The full Chipp MCP has hundreds of tools, so connecting all of it costs tens of thousands of input tokens per message before you type a word.

So Chipp is split into small MCPs, one per area. Each has its own URL, lists only its own tools, and uses the same Chipp sign-in and permissions as the full server.

💡

Recommended: connect core first, then add only the MCPs for the work you do. You can add or remove one at any time.

The MCPs

IDNameWhat it coversURLToolsTokens per message
coreCoreWho you are, workspaces, finding agents, Chipp docs, and the list of the other Chipp MCPs.https://mcp.chipp.ai/mcp/core12about 2,600
appsAgentsCreate, publish, version, chat with and move agents; system prompt, model, suggestions, variables and agent links.https://mcp.chipp.ai/mcp/apps35about 8,300
app-settingsAgent settingsThe full agent settings writers (update_app, bulk_update_app_settings), branding, auth, access lists, tool overrides and workspace defaults.https://mcp.chipp.ai/mcp/app-settings16about 14,300
knowledgeKnowledgeKnowledge sources (URLs, sitemaps, text, documents), crawls, and evidence search over an agent’s knowledge base.https://mcp.chipp.ai/mcp/knowledge20about 4,200
actionsActions and componentsCustom actions, action collections, custom components, and database connections.https://mcp.chipp.ai/mcp/actions32about 11,100
integrationsIntegrationsHosted integrations and their catalog, and MCP servers connected to an agent.https://mcp.chipp.ai/mcp/integrations10about 2,400
analyticsAnalytics and evalsConversations, messages, usage and engagement analytics, end users and their memories, and evals.https://mcp.chipp.ai/mcp/analytics28about 7,200
tagsTagsConversation tags, their training examples and utterances, and tag instances.https://mcp.chipp.ai/mcp/tags15about 4,600
channelsChannelsSlack, email, WhatsApp, GitHub, Discord and voice deployments, and heartbeat schedules.https://mcp.chipp.ai/mcp/channels16about 6,900
billingBilling and monetizationThe subscription, credits, usage and capabilities, and consumer packages an agent sells.https://mcp.chipp.ai/mcp/billing10about 1,700
newslettersNewslettersNewsletter topics, audiences, contacts, campaigns and sends.https://mcp.chipp.ai/mcp/newsletters16about 4,200
projectsSoftware factory projectsSoftware factory projects: list, create and scope them, and the factory tools in no other sub-MCP.https://mcp.chipp.ai/mcp/projectssoftware factoryabout 40,000
ticketsTicketsSoftware factory tickets: list, read, file, reply, retry, cancel, proposals, and child projects.https://mcp.chipp.ai/mcp/ticketssoftware factoryabout 28,000
releasesReleasesSoftware factory deploys and releases: history, the deploy gate, Deploy now, rollbacks, recalls and the release digest.https://mcp.chipp.ai/mcp/releasessoftware factoryabout 7,500
observabilityObservabilityA deployed project’s database (read), logs, errors, analytics, CI status, custom actions, credentials and cost.https://mcp.chipp.ai/mcp/observabilitysoftware factoryabout 11,400
data-opsData operationsChanges to a deployed project’s live data: data, script and procedure operations, bulk ingest, and file exports.https://mcp.chipp.ai/mcp/data-opssoftware factoryabout 11,000
packsPacksThe feature pack and recipe catalog, pack installs, checkout, and the project blueprint.https://mcp.chipp.ai/mcp/packssoftware factoryabout 4,000
memoryMemory and schedulesA project’s memory and task list, circles, and scheduled tasks.https://mcp.chipp.ai/mcp/memorysoftware factoryabout 6,500
legacy-codeLegacy codeThe app or website being rebuilt: its imported GitHub repo, legacy codebase, and crawled site.https://mcp.chipp.ai/mcp/legacy-codesoftware factoryabout 1,164
(all)EverythingEvery tool in one MCP.https://mcp.chipp.ai/mcp209 + software factoryabout 156,900

Token sizes are approximate: they are the tool definitions your model reads on each message, for an account with every permission. The Tools column counts the Chipp tools each MCP lists. The software factory MCPs list tools only when your organization has connected the software factory.

The core MCP has a list_chipp_mcps tool, so you can also ask your assistant “which Chipp MCP do I need for this?”.

Which ones should I add?

You want to…Add
Find agents and read Chipp docscore
Create agents, edit prompts and modelscore, apps
Change settings, branding, auth or accesscore, app-settings
Manage knowledge sourcescore, knowledge
Read conversations and analyticscore, analytics
File and follow software factory ticketscore, tickets
Ship, roll back or check deployscore, releases

Add one to your client

The steps are the same as for the full server; only the URL changes. In Chipp, Settings > Developer (the MCP connection card) has a picker that copies each URL.

  • Claude app / Claude Cowork: add a custom connector with the MCP’s URL, for example https://mcp.chipp.ai/mcp/core. Add one connector per MCP. See Connect from Claude App or Claude Cowork.
  • Claude Code:
    bash
    claude mcp add --transport http chipp-core https://mcp.chipp.ai/mcp/core
    claude mcp add --transport http chipp-tickets https://mcp.chipp.ai/mcp/tickets
  • ChatGPT (connectors in developer mode): create a connector with the MCP’s URL and sign in with Chipp.
  • Cursor and other clients: use the MCP’s URL as the server URL. See Setup & Installation.

Each MCP asks you to sign in the first time (the same Chipp account and the same approval screen). An API key works on every MCP URL.

The full server

https://mcp.chipp.ai/mcp (also https://build.chipp.ai/mcp) still lists every tool, and existing connections keep working. Use it only if you want everything in one place and accept its size (the (all) row in the table).