Mcp App Builder

This walks you through the full lifecycle of building MCP apps, which are conversational tools that extend AI assistants through custom UIs and server-side logic. It covers everything from initial brainstorming against UX guidelines to deploying via Alpic and publishing to ChatGPT or Claude directories. The core insight here is smart: it reminds you that your app serves two users at once, the human and the LLM, and they collaborate through a shared view surface. Use this when you're working with the Skybridge framework or building MCP servers. It's structured as a guided workflow with specific references for each phase, from bootstrapping to OAuth to CSP configuration.

skills.sh installs: 203
GitHub stars: 2.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alpic-ai/skybridge --skill mcp-app-builder --agent claude-code

Installs into .claude/skills of the current project.

Files

Creating MCP Apps

Those are conversational experiences that extend AI assistants through tools and custom UI views. They're built as MCP servers invoked during conversations.

⚠️ The app is consumed by two users at once: the human and the AI Assistant LLM. They collaborate through the view—the human interacts with it, the LLM sees its state. Internalize this before writing code: the view is your shared surface.

SPEC.md keeps track of the app's requirements and design decisions. Keep it up to date as you work on the app.

No SPEC.md? → Read discover.md first. Nothing else until SPEC.md exists.

SPEC.md exists? → Read SPEC.md, then follow architecture.md to design the change. Update SPEC.md, then read the relevant Implementation references below before writing code.

Migrating from Skybridge < 0.36.x? → Read migrate-to-v1.md first. Users may reference skybridge >= 0.36.x as v1.

Migrating from Skybridge 1.x to 2.x? → Fetch the v2.0.0 release notes first and follow them.

SKILL.md on GitHub