> ## 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.

# Content in Metabind

> How Metabind's headless content platform fits alongside the MCP App platform

Metabind is The Agentic Layer for your App, and content management is a first-class capability — every project has content types, content entries, and assets that can be edited in MCP App Studio, queried by client apps, and rendered through MCP Apps.

This tab covers Metabind's content surface: how to model content, how to manage it, how to query it from your applications, and how MCP Apps consume content alongside Tools.

## What "content" means in Metabind

| Term              | What it is                                                                                |
| ----------------- | ----------------------------------------------------------------------------------------- |
| **Content type**  | A schema describing a content shape (e.g., "Article" with fields title, body, hero image) |
| **Content entry** | An instance of a content type (a specific article, with real values)                      |
| **Asset**         | A file (image, video, PDF, 3D model) referenced by content                                |
| **Folder**        | An organizational container for content entries                                           |
| **Tag**           | A label applied to entries for search and filtering                                       |

These map directly to the headless CMS shape teams know from Contentful, Sanity, Strapi, or similar platforms. The difference is what they connect to: Metabind's content can be rendered by BindJS components in mobile apps, served via REST and GraphQL APIs, *and* fed into MCP Tools so AIs can read or modify it.

## Where to manage content

In MCP App Studio:

* **Content** tab in the project sidebar — list, search, create, edit, publish content entries.
* **Content Types** tab — define and version the schemas content entries follow.
* **Assets** tab — upload, manage, and reuse assets across entries.

Editors can work without touching code. Engineers can use the REST or GraphQL APIs for bulk operations.

## Where to consume content

Three pathways:

| Consumer               | Use                                                            |
| ---------------------- | -------------------------------------------------------------- |
| **Native mobile app**  | Use the iOS/Android SDK to fetch content + render via BindJS   |
| **Web app or backend** | Use the REST or GraphQL API                                    |
| **MCP App**            | Pair an Interactive Tool with a Data Tool that fetches content |

The MCP App pathway is the newest. A Data Tool can query Metabind's GraphQL API to fetch content entries; an Interactive Tool can render them as native UI inside an AI conversation. This is how the same content backs both your mobile app and your MCP App.

## Content vs. Types/Tools

The platform now has two related-but-distinct registration units:

* **Types** are MCP Tools — Interactive Tools or Data Tools the AI can call. See the Guides tab for the MCP App platform.
* **Content types** are CMS schemas — content entries the AI (or your app) can read/write.

A project can have both. They live in separate sidebars in MCP App Studio. They interact through Data Tools — a Data Tool can read or write content via the [Content API](/content/querying/overview), giving the AI controlled access to your headless content.

## Content delivery APIs

| API                                       | Use for                                               |
| ----------------------------------------- | ----------------------------------------------------- |
| [REST API](/rest/introduction)            | Server-to-server, bulk operations, auth-heavy flows   |
| [GraphQL API](/content/querying/overview) | Apps that need flexible queries, single-request joins |
| iOS SDK / Android SDK                     | Native mobile apps with offline + caching             |

All three speak the same content model. Pick whichever fits your client.

## AI-driven content workflows

Content can be created and updated by AIs — useful for:

* **Drafting articles or product descriptions** with AI assistance, edited by a human, published when ready.
* **Bulk migration** of content from another CMS using an AI agent that maps fields.
* **Operations** like archiving stale entries, tagging by topic, or normalizing metadata.

The content-management MCP server exposes context, discovery, and creation tools. See [AI content creation](/content/ai-content-creation/overview).

## Where to go next

<CardGroup cols={2}>
  <Card title="Managing content" icon="folder-open" href="/content/managing/overview">
    Editor workflow in MCP App Studio.
  </Card>

  <Card title="Querying content" icon="magnifying-glass" href="/content/querying/overview">
    REST, GraphQL, and SDKs for client apps.
  </Card>

  <Card title="AI content creation" icon="wand-magic-sparkles" href="/content/ai-content-creation/overview">
    Using AI to draft, modify, and migrate content.
  </Card>

  <Card title="Mobile SDKs" icon="mobile" href="/content/mobile-sdks/overview">
    Native iOS and Android content fetching with BindJS rendering.
  </Card>
</CardGroup>