Skip to main content
The MCP (Model Context Protocol) Content Creation Tools enable AI agents to discover, understand, and create content within the Metabind platform’s established design system structures. These tools are optimized for LLM usage, returning only the fields necessary for content understanding and generation while minimizing token consumption.

​
Key Principles

​
Minimal Token Usage

  • Returns only fields needed for content creation
  • Excludes internal metadata and system fields
  • Full schemas and content only returned when explicitly requested via get operations
  • Descriptions use structured markdown for better LLM comprehension

​
Schema-Driven Creation

  • All content creation validated against JSON schemas
  • Content stored as structured JSON matching schemas
  • Compiled BindJS code auto-generated from JSON
  • Type safety through schema validation

​
Semantic Discovery

  • Vector search capabilities for finding relevant resources
  • Natural language queries for content and component discovery
  • AI-optimized descriptions using structured markdown
  • Leverages embeddings for conceptual similarity matching

​
Design System Compliance

  • Ensures all created content follows established patterns
  • Validates against content type constraints
  • Maintains component allowlists and groupings
  • Preserves package version dependencies

​
Dual Search Modes

All search tools support two modes:
ModeTriggerBehavior
Semantic SearchInclude query parameterUses AI embeddings for natural language queries, returns relevance-ranked results
Standard FilteringOmit query parameterUses exact matching on filters, returns consistently ordered results
Combine semantic search with filters for precise, relevant results.

​
Tool Categories

Context Management

Set and manage project context for all operations

Content Discovery

Search and retrieve content types and content items

Component Discovery

List and search available components

Asset Management

Search and discover media assets

Content Creation

Create and update content items

Error Handling

Validation errors and recovery strategies

​
Tool Summary

CategoryToolDescription
Contextset_projectSet default project context
get_current_projectGet current project context
list_projectsList available projects
Content Discoverysearch_content_typesSearch/list content types
get_content_typeGet detailed content type schema
search_contentSearch/list content items
get_contentGet detailed content item
Componentslist_componentsList components with semantic search
Assetssearch_assetsSearch/list media assets
Creationcreate_contentCreate new content items
update_contentUpdate existing content

​
Naming Conventions

ElementConventionExample
Tool namessnake_casesearch_content_types
Field namescamelCasecontentTypeId
Response fieldscamelCaseprojectName
This maintains MCP consistency for tool names while matching the Metabind API’s camelCase field naming.

​
Authentication

MCP tools use the same authentication as the Metabind API. The MCP server handles authentication through the connection parameters established when the client connects.

​
Project Context

All tools accept an optional projectId parameter. If not provided, tools use the session’s default project set via set_project. Context persists within a session but requires re-establishment on reconnection. 
// Set project context once
await mcp.call("set_project", { projectId: "proj_123" });

// Subsequent calls use the default project
await mcp.call("search_content", { query: "tutorials" });