Catalog schemas
Use these references when authoring MCP server and vMCP definitions in Git. A catalog entry defines how a server runs or where it is reached. A separate type: vmcp item defines components, configuration policies, tool selections, and profiles.
| Format | Reference |
|---|---|
| Catalog metadata, runtime, configuration values, and resource requirements | Catalog YAML structure |
| Supported Obot versions for an entry | Obot version range |
| Catalog file selection and validation | Selecting files and CLI validation |
| vMCP components, profiles, and fixed configuration | vMCP definitions |
| Registry contribution example | MCP Registry API |
| Per-server domain egress settings | Egress YAML examples |
| OpenAPI schema sources and credential configuration | OpenAPI GitOps examples and import requirements |
Validate changes with obot mcp validate-catalog before synchronizing a source. The validator for the installed Obot version is authoritative for supported fields. runtime: composite is not accepted; build endpoints from catalog entries using Create vMCP.
For existing Git-synced composites, use the migration command to generate matching vMCP definitions while retaining component IDs and connections. See Git Catalogs for source setup and validation commands.