santhotech

Agentic Host Starter Kit — AI skill for Claude Code

AI community

Open-source starter kit for building your own AI chat host that renders MCP Apps.

How to install Agentic Host Starter Kit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open santhotech/agentic-host-starter-kit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agentic Host Starter Kit does

Open-source starter kit for building your own AI chat host that renders MCP Apps. Connect any MCP servers (stdio or HTTP), chat with Claude, and render interactive tool UIs inline in a secure sandboxed iframe. Agent loop, AppBridge wiring, CSP sandbox, tool approvals and a React UI included. TypeScript + Model Context Protocol.

Alternatives in AI

MCP Use — The fullstack MCP framework to develop MCP Apps for ChatGPT / Claude & MCP Servers for AI Agents 9.5k ★
Gh PR Review — GitHub CLI extension that adds full inline PR review comment support — view, navigate, reply to, and resolve r 174 ★
Chat Plus — Make your ai chat smarter 123 ★

README

agentic-host-starter-kit

**Build your own AI chat host that renders MCP Apps.**

Connect any MCP servers, chat with Claude, and let their interactive UIs render inline, securely sandboxed, in an app you own.

![License](https://img.shields.io/badge/license-Apache--2.0-blue) ![Node](https://img.shields.io/badge/node-%3E%3D22-339933) ![TypeScript](https://img.shields.io/badge/TypeScript-5.x-3178C6) ![MCP Apps](https://img.shields.io/badge/MCP%20Apps-2026--01--26-6E56CF)

Why this exists

[MCP Apps](https://modelcontextprotocol.io/extensions/apps/overview) is the first official extension to the Model Context Protocol. It lets an MCP server ship an **interactive UI with its tools**: a hotel picker, an approval queue, a chart. The host renders it right inside the conversation instead of a wall of text.

Today, those UIs only render inside a handful of big hosts: Claude, ChatGPT, VS Code, Cursor, M365 Copilot and a few dev tools. If you want them inside **your own product** (a vertical assistant, an internal copilot, a customer-facing agent), you start from scratch: an MCP client per server, an agent loop, a sandbox on a separate origin, the AppBridge handshake, CSP, consent for actions that change things...

**This kit is that scaffolding, done properly, in a codebase small enough to read in an afternoon.** Clone it, point it at your servers, make it yours.

What it solves

Without it	With it
MCP Apps only render in someone else's chat app	They render in yours
Hand-rolled iframes on your own origin (an app can read your cookies)	Double-iframe sandbox on a separate origin, CSP sent as an HTTP header
Apps calling servers directly from the browser	Every app tool call goes through your backend, only to the app's own server
Agents quietly doing things with side effects	Tools that write need the user's OK, whether the model or an app asked
One-off integrations per vendor	An