Chaps - Apps you can chat with.

Distribute your MCPs directly to users

TL;DR : Chaps enables you to wrap your MCP, and enable ordinary users to interact with it. We provide both UX and functional improvements on top of the MCP server you already (might) have, as well as a simple way to let any user interact with it.

In other words, it's like an app store for Chat First Apps.

Why Build on Chaps?

Pain Today	Chaps Fix
Non‑technical users can't run your MCP or CLI	One‑click deploy. Share a link or QR code; Chaps launches the Chap instantly in the browser or mobile app.
MCPs only available inside developer tools	Web & native clients. The same Chap runs on iOS, Android, and any modern browser. Email & voice channels on the roadmap.
OAuth screens, token storage, refresh logic	One‑line auth. Declare `type: oauth` or `apiKey`; Chaps handles consent, secure storage, and token refresh.
Session tables, preference pages, feature flags	Memory & inference. Chaps remembers context, learns user preferences, and adapts tone automatically.
Can't distribute without heavy infra investment	Hosted runtime. Real‑time connections, sandboxed VMs, and scaling are managed for you. Go live in 5 min, free tier included.
Can't charge for my creation	Payments built‑in. Offer in‑chat purchases or subscriptions; Chaps processes payments and handles payouts & taxes.

Why Wrap MCPs?

MCPs are powerful but they're just tools - they lack context about their environment and users. This gap creates real problems:

Environmental Context: A Google Calendar MCP doesn't know the user's timezone or current time. A weather MCP doesn't know the user's location. LLMs don't have this information unless explicitly provided.

User-Specific Context: Your MCP doesn't know how each user prefers to use it. Does Sarah always schedule meetings at 30-minute intervals? Does Tom prefer military time? These preferences matter for usability.

Platform Capabilities: Raw MCPs lack essential features users expect:

Authentication: OAuth flows, token management, secure storage
Memory: Conversation history, user preferences, learned patterns
Scheduling: Recurring tasks, reminders, time-based actions
Data Persistence: Caching frequently used data, maintaining state

Chaps bridges this gap. We provide the context layer that makes your MCP actually useful - handling auth, remembering preferences, understanding context, and delivering a complete user experience. You focus on your tools; we handle everything else.

What You Ship

(Optional) MCP Server – an adapter that exposes your API as structured tools. Publish it as npx your-mcp or host it at https://…/mcp/. Some chaps may not need a server at all - only a great prompt.
Chap Configuration – a 20‑30 line YAML/JSON file that tells Chaps:
- agent name & goal
- where the MCP server lives (remote or local)
- how to authenticate (oauth or apiKey)
- any usage hints or data to cache
- styling options like colors and icons

id: com.acme.tickets
name: TicketBot
developer: Acme Inc.
core:
  name: TicketBot
  mainGoal: Create & update Zendesk tickets by chat
  mainBehavior: |-
    Provide a short, structured summary after every ticket is filed.
mcpServers:
  - name: zendesk
    server:
      type: remote
      url: https://api.acme-zendesk-mcp.com/
    auth:
      type: oauth

Time to "Hello, world": under 5 minutes if you already have an API.

How It Works at Runtime

User types "raise a P1 bug: checkout fails".
Chaps calls your MCP tool zendesk_create_ticket.
Your server returns JSON (e.g., new ticket ID).
Chaps summarizes the result back to the user and stores context for follow‑ups like "close that bug".

Next Steps

If interested in building a Chap, please fill out our developer beta form to get started. Once approved, you will get access to our developer portal and documentation.