MCP Kafka Schema Reg
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIEWONLY | No | Enable read-only mode for production safety | false |
| SLIM_MODE | No | Reduce tool count from 57+ to ~9 essential tools for better performance | false |
| VIEWONLY_1 | No | Read-only mode for the first registry | |
| VIEWONLY_2 | No | Read-only mode for the second registry | |
| ENABLE_AUTH | No | Enable OAuth 2.1 authentication | |
| AUTH_AUDIENCE | No | OAuth audience/client ID | |
| AUTH_ISSUER_URL | No | OAuth provider issuer URL | |
| SCHEMA_REGISTRY_URL | No | The URL of the schema registry server | |
| SCHEMA_REGISTRY_USER | No | Optional authentication username for schema registry | |
| SCHEMA_REGISTRY_URL_1 | No | URL for the first registry in multi-registry mode | |
| SCHEMA_REGISTRY_URL_2 | No | URL for the second registry in multi-registry mode | |
| SCHEMA_REGISTRY_NAME_1 | No | Name for the first registry in multi-registry mode | |
| SCHEMA_REGISTRY_NAME_2 | No | Name for the second registry in multi-registry mode | |
| SCHEMA_REGISTRY_PASSWORD | No | Optional authentication password for schema registry |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsB | List available multi-step workflows |
| describe_workflowC | Get detailed information about a workflow definition |
| guided_schema_evolutionC | Start the Schema Evolution Assistant workflow. This guided workflow helps you safely evolve schemas by analyzing changes, suggesting strategies, and coordinating consumer updates. |
| pingA | Respond to MCP ping requests with pong. This tool implements the standard MCP ping/pong protocol for server health checking. MCP proxies and clients use this to verify that the server is alive and responding. |
| compare_registriesC | Compare two Schema Registry instances and show differences. |
| compare_contexts_across_registriesC | Compare contexts across two registries. |
| find_missing_schemasB | Find schemas that exist in source registry but not in target registry. |
| list_available_resourcesB | List all available MCP resources and their usage patterns. |
| suggest_resource_for_toolC | Suggest the appropriate resource to use instead of a removed tool. |
| generate_resource_templatesC | Generate resource URI templates for your specific configuration. |
| list_registriesA | List all configured Schema Registry instances. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://names' resource instead for better performance. |
| get_registry_infoB | Get detailed information about a specific registry. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://info/{name}' resource instead for better performance. |
| test_registry_connectionB | Test connection to a specific registry. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://status/{name}' resource instead for better performance. |
| test_all_registriesA | Test connections to all configured registries. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://status' resource instead for better performance. |
| list_subjectsB | List all subjects, optionally filtered by context. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://{name}/subjects' resource instead for better performance. |
| get_schemaA | Get a specific version of a schema. NOTE: This tool is maintained for backward compatibility. Consider using the 'schema://{name}/{context}/{subject}' resource instead for better performance. |
| get_schema_versionsA | Get all versions of a schema for a subject. NOTE: This tool is maintained for backward compatibility. Consider using the 'schema://{name}/{context}/{subject}/versions' resource instead for better performance. |
| get_schema_by_idC | Get a schema by its globally unique ID. |
| get_subjects_by_schema_idB | Get subjects and versions associated with a schema ID. |
| get_global_configB | Get global configuration settings. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://{name}/config' resource instead for better performance. |
| get_modeA | Get the current mode of the Schema Registry. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://mode' resource instead for better performance. |
| list_contextsB | List all available schema contexts. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://{name}/contexts' resource instead for better performance. |
| get_subject_configB | Get configuration settings for a specific subject. NOTE: This tool is maintained for backward compatibility. Consider using the 'subject://{name}/{context}/{subject}/config' resource instead for better performance. |
| get_subject_modeB | Get the operational mode for a specific subject. NOTE: This tool is maintained for backward compatibility. Consider using the 'subject://{name}/{context}/{subject}/mode' resource instead for better performance. |
| register_schemaC | Register a new schema version. |
| register_schema_interactiveB | Interactive schema registration with elicitation for missing field definitions. When schema_definition is incomplete or missing fields, this tool will elicit the required information from the user interactively. |
| check_compatibilityC | Check if a schema is compatible with the latest version. |
| check_compatibility_interactiveC | Interactive compatibility checking with elicitation for resolution options. When compatibility issues are found, this tool will elicit resolution preferences from the user. |
| add_subject_aliasB | Create a subject alias to an existing subject (not available in SLIM/VIEWONLY). |
| export_schemaC | Export a single schema in the specified format. |
| export_subjectC | Export all versions of a subject. |
| export_contextC | Export all subjects within a context. |
| export_globalC | Export all contexts and schemas from a registry. |
| export_global_interactiveB | Interactive global export with elicitation for export preferences. When export preferences are not specified, this tool will elicit the required configuration from the user. |
| count_contextsC | Count the number of contexts in a registry. |
| count_schemasB | Count the number of schemas in a context or registry. |
| count_schema_versionsC | Count the number of versions for a specific schema. |
| get_registry_statisticsC | Get comprehensive statistics about a registry. |
| get_mcp_compliance_statusA | Get MCP 2026-07-28 specification compliance status and configuration details. Returns information about JSON-RPC batching status, protocol version, header validation, and migration guidance. |
| get_default_registryC | Get the current default registry. |
| get_oauth_scopes_infoC | Get information about OAuth scopes and permissions. |
| test_oauth_discovery_endpointsA | Test OAuth discovery endpoints to ensure proper MCP client compatibility. Validates:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| schema-getting-started | Getting started with Schema Registry operations |
| schema-registration | Guide for registering new schemas |
| schema-export | Guide for exporting schemas and documentation |
| schema-compatibility | Guide for schema compatibility and evolution |
| troubleshooting | Troubleshooting guide for common issues |
| schema-evolution | Guide for safe schema evolution with the Schema Evolution Assistant |
| quick-reference | Get a quick reference card of most common commands. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| registry_names_resource | Get list of all configured registry names. |
| registry_info_resource | Get detailed server configuration and capabilities. |
| registry_status_resource | Get connection status for all registries. |
| registry_mode_resource | Get operational mode for all registries. |
TDQS
Scored across 42 tools
Many tools target distinct operations, but there are several overlapping pairs such as register_schema vs register_schema_interactive, check_compatibility vs check_compatibility_interactive, and export_global vs export_global_interactive. Deprecated tools are explicitly noted as replaceable by resources, which creates ambiguity about whether an agent should call the tool or use the resource. The descriptions help, but the set still has notable boundary confusion.
Most tools follow a predictable snake_case verb_noun pattern, including clear prefixes like get_, list_, test_, export_, and count_. The interactive variants use a consistent _interactive suffix. Minor deviations such as ping and guided_schema_evolution keep it from being perfectly uniform.
With 42 tools, the surface is heavy for a Schema Registry server, especially because many tools are explicitly maintained only for backward compatibility and point to resources instead. The large number of near-duplicate interactive/non-interactive variants and deprecated tools makes the set feel bloated rather than well-scoped.
The tools cover many read operations, registration, compatibility checks, exports, counts, statistics, and registry comparisons. However, write-side lifecycle operations such as deleting subjects or schema versions and setting global/subject config or mode appear missing, leaving notable gaps. Agents can perform many workflows but may hit dead ends for administrative mutations.