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
  • Response fields carefully selected to balance utility and token consumption

​
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: Combine semantic search with filters for precise, relevant results.

​
Getting Started

Configure your MCP client to connect to:
Authentication uses the same API key as other Metabind endpoints.

​
Tool Categories

Context Management

Set and manage project context for all operations

Discovery Tools

Search and retrieve content types, content items, components, and assets

Content Creation

Create and update content items

Error Handling

Validation errors and recovery strategies

​
Tool Summary

​
Naming Conventions

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.