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 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_workflowC | Start a multi-step workflow for complex Schema Registry operations |
| list_workflowsB | List available multi-step workflows |
| workflow_statusC | Get the status of active workflows |
| abort_workflowB | Abort an active workflow |
| describe_workflowB | 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. |
| guided_schema_migrationC | Start the Schema Migration Wizard workflow for guided schema migration |
| guided_context_reorganizationC | Start the Context Reorganization workflow for reorganizing schemas across contexts |
| guided_disaster_recoveryB | Start the Disaster Recovery Setup workflow for configuring DR strategies |
| 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_registriesD | Compare contexts across two registries. |
| find_missing_schemasC | 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_templatesD | 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_infoA | 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_subjectsA | 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_schemaB | 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_idB | Get a schema by its globally unique ID. Args: schema_id: The globally unique schema ID registry: Optional registry name (ignored in single-registry mode) Returns: Schema information including content, type, and metadata |
| get_subjects_by_schema_idC | Get subjects and versions associated with a schema ID. Args: schema_id: The globally unique schema ID registry: Optional registry name (ignored in single-registry mode) Returns: List of subject-version pairs that use this schema ID |
| get_global_configA | Get global configuration settings. NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://{name}/config' resource instead for better performance. |
| get_modeB | 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_contextsA | 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_configA | 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_modeA | 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. |
| update_global_configD | Update global configuration settings. |
| update_subject_configC | Update configuration settings for a specific subject. |
| update_modeC | Update the mode of the Schema Registry. |
| update_subject_modeC | Update the mode for a specific subject. |
| create_contextC | Create a new schema context. |
| create_context_interactiveC | Interactive context creation with elicitation for metadata. When context metadata is not provided, this tool will elicit organizational information from the user. |
| delete_contextC | Delete a schema context. |
| delete_subjectB | Delete a subject and all its versions. Args: subject: The subject name to delete context: Optional schema context registry: Optional registry name permanent: If True, perform a hard delete (removes all metadata including schema ID) |
| 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_interactiveC | Interactive global export with elicitation for export preferences. When export preferences are not specified, this tool will elicit the required configuration from the user. |
| migrate_schemaC | Migrate a schema from one registry to another. |
| list_migrationsB | List all migration tasks and their status. |
| get_migration_statusC | Get detailed status of a specific migration. |
| migrate_contextC | Guide for migrating an entire context using Docker-based tools. |
| migrate_context_interactiveC | Interactive context migration with elicitation for missing preferences. When migration preferences are not specified, this tool will elicit the required configuration from the user. |
| clear_context_batchC | Clear all subjects in a context using application-level batch operations. ⚠️ APPLICATION-LEVEL BATCHING: Uses individual requests per MCP 2025-06-18 compliance. |
| clear_multiple_contexts_batchC | Clear multiple contexts in a registry using application-level batch operations. ⚠️ APPLICATION-LEVEL BATCHING: Uses individual requests per MCP 2025-06-18 compliance. |
| bulk_operations_wizardC | Start the interactive Bulk Operations Wizard for admin tasks. Guides through safe execution of operations across multiple schemas. Supports schema updates, migrations, cleanup, and configuration changes. |
| bulk_schema_updateC | Update schemas in bulk with interactive guidance. Supports compatibility settings, naming conventions, and metadata updates. Pattern matching supported (e.g., test-, deprecated-). |
| bulk_schema_cleanupB | Clean up schemas in bulk with safety checks. Detects active consumers and provides options for handling them. Supports test schema cleanup, deprecated schema removal, and version purging. |
| bulk_schema_migrationC | Migrate schemas between contexts or registries. Supports pattern-based selection and maintains schema IDs. Includes preview and rollback capabilities. |
| bulk_configuration_updateC | Update configuration settings across multiple schemas or contexts. Supports security policies, retention settings, and access controls. |
| count_contextsC | Count the number of contexts in a registry. |
| count_schemasC | 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. |
| list_elicitation_requestsB | List all pending elicitation requests. |
| get_elicitation_requestC | Get details of a specific elicitation request. |
| cancel_elicitation_requestC | Cancel a pending elicitation request. |
| get_elicitation_statusC | Get the status of the elicitation system. |
| submit_elicitation_responseC | Submit a response to an elicitation request. This tool handles both regular elicitation responses and multi-step workflow responses. When a workflow is in progress, it will automatically advance to the next step. |
| list_available_workflowsB | List all available multi-step workflows for complex operations. |
| get_workflow_statusC | Get the status of active workflows. |
| get_task_statusC | Get the status and progress of an async task. |
| get_task_progressC | Get the progress of an async task (alias for get_task_status). |
| list_active_tasksB | List all active tasks in the system. |
| cancel_taskC | Cancel a running task. |
| list_statistics_tasksB | List all statistics-related tasks. |
| get_statistics_task_progressC | Get detailed progress for a statistics task. |
| get_mcp_compliance_status_toolB | Get MCP 2025-06-18 specification compliance status and configuration details. Returns information about JSON-RPC batching status, protocol version, header validation, and migration guidance. |
| set_default_registryD | Set the default registry. |
| get_default_registryB | Get the current default registry. |
| get_oauth_scopes_info_toolB | Get information about OAuth scopes and permissions. |
| test_oauth_discovery_endpointsA | Test OAuth discovery endpoints to ensure proper MCP client compatibility. Validates:
Args: server_url: Base URL of the MCP server (default: http://localhost:8000) Returns: Dictionary with test results for each discovery endpoint |
| get_operation_info_toolC | Get detailed information about MCP operations and their metadata. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
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. |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aywengo/kafka-schema-reg-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server