Skip the protocol boilerplate, the hosting, and the schema plumbing. Define your tools, press publish, and your MCP server is live on Claude, ChatGPT, VS Code, and every MCP-compatible host. The same definition embeds inside your own iOS, Android, or web app as a native AI assistant.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.
Start free
No credit card. No server to manage. Publish your first MCP App in minutes.
Five-minute walkthrough
Clone the Oak & Ivory retail sample and watch native product cards render in Claude Desktop.
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 anasync handler that runs in a V8 sandbox with your secrets injected at runtime. No credentials in client code, no hosting to manage.
And 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 — rendered as SwiftUI on iOS, Jetpack Compose on Android, and React on the web. From a single BindJS component definition. No WebViews. No bespoke renderer per surface..png)
Skip the parts that aren’t your product
| 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 |
Three tool types, one MCP App
Data Tools
Wrap any REST or GraphQL endpoint as an MCP tool. Handlers run in V8 sandboxes with injected secrets. Credentials never reach the client.
Interactive Tools
Return schema-validated native UI instead of JSON. Component allowlists enforce what can render. Same definition on iOS, Android, web.
Content Tools
Documents and assets served through semantic search. The AI retrieves rich content via MCP tool calls.
How it works
Define tools in MCP App Studio
Author Data Tools and Interactive Tools in the visual builder. Live preview as you go — on a real device, not a simulator. The draft endpoint is testable from the first save.

Test against the draft endpoint
Every project ships with 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 can connect with the URL. Hosts pick up new tool versions on their next list-tools call.Built on the open MCP protocol
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 — today and going forward.Common questions
How is this different from building my own MCP server?
How is this different from building my own MCP server?
A from-scratch MCP server means writing transport conformance, schema validation, hosting, secret management, and a UI renderer per surface — and then re-doing it every time the protocol evolves. Metabind ships all of that as a managed platform. You write the tools that are unique to your product; everything else is provided.
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, Assistant SDK included, 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) is MIT-licensed and 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.Ship today
Start free
No credit card. No server to manage. Publish your first MCP App in minutes.
Your first MCP App
Five minutes, no code, Oak & Ivory product cards rendering inline in Claude Desktop.
Build a Data Tool
The full Data Tool authoring guide — secrets, allowed domains, sandbox limits.
Connect to Claude Desktop
Point Claude Desktop at your draft or production MCP server URL.