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.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.
Wrap any API as an MCP tool
A Metabind Data Tool is a typed function the AI can call. You declare an input schema, an output schema, and a handler that runs in a V8 sandbox with your secrets injected at runtime — so credentials never reach the client, and there’s no server to host or scale. Point a handler at any REST or GraphQL endpoint and it’s an MCP tool.Get native UI from one tool call
Most MCP servers return JSON dumps. Metabind’s Interactive Tools return real, schema-validated native UI — product cards, comparison tables, galleries, 3D viewers — from a single BindJS component definition. When the AI calls the tool, Metabind validates its response against your schema and renders only components from your published allowlist. The AI can’t inject anything you didn’t approve, on any platform..png)
How it works
Author tools in MCP App Studio
Build Data Tools and Interactive Tools in the visual builder, with live previews on a real device as you go. Everything is testable from the first save.
Test against the draft endpoint
Every project ships two MCP server URLs — a draft endpoint that serves everything (published, modified, draft) and a production endpoint that serves only published work. Point Claude Desktop at the draft URL while you iterate.
Publish to every MCP host
One button promotes the draft to
mcp.metabind.ai/<your-org>/<your-project>. Claude Desktop, ChatGPT, VS Code, and any MCP-compatible host connect with the URL.Two distribution surfaces, one MCP App
| Surface | What ships | Renderer |
|---|---|---|
| Every MCP host | Hosted 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 app | The Assistant SDK — metabind-ai-apple and metabind-ai-android. | Native SwiftUI or Jetpack Compose directly in your app. |
What you don’t build
| You’d normally build | Metabind handles |
|---|---|
| Protocol boilerplate, transport, host conformance | Hosted MCP server on mcp.metabind.ai |
| Tool input/output schema plumbing | Auto-generated from your component definitions |
| Server hosting, scaling, monitoring | Auto-scaling multi-tenant infrastructure on AWS |
| UI rendering code per platform | SwiftUI, Compose, and React from one BindJS definition |
| Visual tooling for authoring + previews | MCP App Studio — visual builder, live device previews, sample apps |
| Staging, versioning, rollback | Draft + production endpoints, package versioning, one-button rollback |
How is this different from building your own MCP server?
Building an MCP server from scratch means writing transport and host conformance, schema validation in both directions, secret management, hosting and scaling, and a UI renderer for every surface you want to support — then maintaining all of it as the protocol evolves. Metabind ships that entire layer as a managed platform. You write the tools that are unique to your product; everything underneath — protocol, hosting, validation, governance, and native rendering — is provided and kept current.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.Common questions
Can I use my own components?
Can I use my own components?
Yes. Author BindJS components in MCP App Studio or directly in code. Component allowlists per tool determine which of your components are eligible to render — a
product_search tool can render ProductCard but not AdminTable, enforced at render time.Can I connect my own APIs?
Can I connect my own APIs?
Yes — that’s what Data Tools are. Point a Data Tool handler at any REST or GraphQL endpoint, declare the input and output schema, and the platform handles auth, sandboxing, and schema validation in both directions.
What's the free tier?
What's the free tier?
Starter: MCP App Studio, BindJS, and the Assistant SDK included, with a free invocation allowance. No credit card.
Do I have to use native mobile rendering?
Do I have to use native mobile rendering?
No. The web renderer (
@bindjs/renderer) ships React components into every MCP host’s sandboxed iframe by default. Native SwiftUI and Jetpack Compose rendering is unlocked by the Assistant SDK when you embed the MCP App inside your own iOS or Android app.Start building
Start free
No credit card. Publish your first MCP App in minutes.
Your first MCP App
Five minutes, no code — Oak & Ivory product cards rendering inline in Claude Desktop.
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.