Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.metabind.ai/llms.txt

Use this file to discover all available pages before exploring further.

Metabind is The Native MCP App Platform. You build an MCP App once — Interactive Tools, Data Tools, components in BindJS — and publish it to every MCP host (Claude, ChatGPT, and any other) with one button. The same MCP App also embeds inside your own iOS, Android, or web app as a native AI assistant via the Assistant SDK. The platform’s identity is native rendering: an Interactive Tool’s UI compiles from a single BindJS definition to SwiftUI on iOS, Jetpack Compose on Android, and React on the web. No WebViews. No app-store releases for layout changes. No bespoke renderer per surface.

​
Two distribution surfaces, one MCP App

A single MCP App definition reaches every MCP host (Claude, ChatGPT, others) and embeds inside your own iOS, Android, or web app via the Assistant SDK.
SurfaceWhat shipsRenderer
Every MCP hostHosted MCP server URL on mcp.metabind.ai. Claude Desktop, ChatGPT, and any host that speaks the MCP protocol connect to it.Sandboxed iframe via @bindjs/renderer (React).
Embedded in your appThe Assistant SDK — metabind-ai-apple, metabind-ai-android, @metabind/assistant-sdk.Native SwiftUI, Jetpack Compose, or React directly in your app.
You don’t choose between these. One publish reaches both.

​
What’s in an MCP App

  • Interactive Tools — schema-validated rendered UI returned by tool calls (product cards, comparison tables, charts), not JSON dumps.
  • Data Tools — REST or GraphQL endpoints proxied as MCP tools. Handlers run in V8 sandboxes with secrets injected at runtime; credentials never reach the client.
  • Components — reusable BindJS layouts shared across tools.
  • Project Instructions — guidance the AI receives on connect. Tells the model when to call which tool.
  • Governance — schema validation, component allowlists, package versioning, instant rollback, audit trail. Platform features, not custom infrastructure.

​
What you don’t build

  • Protocol boilerplate, transport, host conformance.
  • MCP server hosting, scaling, monitoring.
  • Schema plumbing for tool inputs and outputs.
  • A UI renderer per platform.
  • Visual tooling for component authoring and previews.
  • Staging, versioning, and rollback workflows.

​
Built on open protocols

Metabind aligns with the open Model Context Protocol per SEP-1724, and Interactive Tools follow SEP-1865 (MCP Apps: Interactive User Interfaces for MCP). Anything you build on Metabind speaks the MCP wire format and runs in any MCP-compatible host.

​
How the rest of these docs are organized

Your first MCP App

Publish a working MCP App to Claude Desktop in five minutes using the Oak & Ivory retail sample.

Core Concepts

The mental model — Types, Components, native rendering, and governance.

Building Your MCP App

The day-to-day authoring workflow — Interactive Tools, Data Tools, BindJS, allowlists, sandbox.

Publishing

Package versioning, publishing the server, rolling back.

Connecting to MCP hosts

Claude Desktop, ChatGPT, and any other MCP host.

Assistant SDK

Embed your MCP App as a native AI assistant inside your iOS, Android, or React app.

Operations

Roles, audit logs, project visibility, SSO.

Sample Apps

Reference MCP Apps you can clone, study, and run end-to-end.

​
Where to start

If you’ve never seen Metabind in action, start with Your first MCP App — five minutes, no code, Oak & Ivory product cards rendering inline in Claude Desktop. Then come back here when you want the conceptual map.