Schema Registry as Tools
mcp-schema-registry · client connects straight to a Karapace-compatible schema registry and exposes subject, schema, and compatibility operations as a fixed set of intrinsic MCP tools. No OpenAPI spec to register, no options.tools to hand-author, no upstream MCP server standing in front of the registry.
Configuration
mcp_schema_registry_client:
type: mcp-schema-registry
kind: client
options:
server: http://karapace-registry.examples.dev:8081
routes:
- when:
- tool: register_schema
guarded:
my_guard:
- kafka-sr:write
- when:
- tool: "*"Route-level guarded: gates register_schema behind a write role, while every read-only tool falls through to the open route. options.server is the only required option: point it at the registry and the full tool set is available immediately.
Tool Set
| Category | Tools |
|---|---|
| Subjects | list_subjects, describe_subject, delete_subject |
| Schemas | register_schema, get_schema, delete_schema_version |
| Compatibility | check_compatibility, get_compatibility, set_compatibility |
None of these tools declare a fixed outputSchema — each one's structuredContent mirrors the registry's own raw JSON response, and its summary interpolates a field or two out of that same response (${result.id}, ${result.compatibilityLevel}) for a human-readable result text. See mcp-schema-registry · client for the full per-tool argument and response reference.
When to Reach for It
Reach for mcp-schema-registry when the operations you need are already in its fixed tool set — subject, schema, and compatibility management against one registry, no schema authoring, no upstream server to run. Pair it with Schema Registry when the same registry also backs a Guardrail's schema validation elsewhere in the same zilla.yaml. See Backend Bindings for how it compares to the other two backend bindings.