Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| READONLY | No | Set to 'true' to enable read-only mode for production safety in single registry mode | false |
| READONLY_1 | No | Set to 'true' to enable read-only mode for the first registry in multi-registry mode | |
| READONLY_2 | No | Set to 'true' to enable read-only mode for the second registry in multi-registry mode | |
| ENABLE_AUTH | No | Set to 'true' to enable OAuth 2.1 authentication | |
| AUTH_AUDIENCE | No | Client ID for OAuth authentication | |
| AUTH_ISSUER_URL | No | URL of the OAuth provider issuer | |
| SCHEMA_REGISTRY_URL | No | URL of the schema registry server in single registry mode | |
| SCHEMA_REGISTRY_USER | No | Optional username for schema registry authentication in single registry mode | |
| 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 password for schema registry authentication in single registry mode |
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| schema-getting-started | |
| schema-registration | |
| context-management | |
| schema-export | |
| multi-registry | |
| schema-compatibility | |
| troubleshooting | |
| advanced-workflows |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_registry_status | Get the current status of Schema Registry connections. |
| get_registry_info_resource | Get detailed information about Schema Registry configurations. |
| get_mode_info | Get information about the current registry mode and how it was detected. |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_elicitation_response | Submit an elicitation response from the client. |
| ping | 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. |
| list_registries | List all configured Schema Registry instances. |
| get_registry_info | Get detailed information about a specific registry. |
| test_registry_connection | Test connection to a specific registry and return comprehensive information including metadata. |
| test_all_registries | Test connections to all configured registries with comprehensive metadata. |
| compare_registries | Compare two Schema Registry instances and show differences. |
| compare_contexts_across_registries | Compare contexts across two registries. |
| find_missing_schemas | Find schemas that exist in source registry but not in target registry. |
| register_schema | Register a new schema version. |
| register_schema_interactive | 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. |
| get_schema | Get a specific version of a schema. |
| get_schema_versions | Get all versions of a schema for a subject. |
| list_subjects | List all subjects, optionally filtered by context. |
| check_compatibility | Check if a schema is compatible with the latest version. |
| check_compatibility_interactive | Interactive compatibility checking with elicitation for resolution options. When compatibility issues are found, this tool will elicit resolution preferences from the user. |
| get_global_config | Get global configuration settings. |
| update_global_config | Update global configuration settings. |
| get_subject_config | Get configuration settings for a specific subject. |
| update_subject_config | Update configuration settings for a specific subject. |
| get_mode | Get the current mode of the Schema Registry. |
| update_mode | Update the mode of the Schema Registry. |
| get_subject_mode | Get the mode for a specific subject. |
| update_subject_mode | Update the mode for a specific subject. |
| list_contexts | List all available schema contexts. |
| create_context | Create a new schema context. |
| create_context_interactive | Interactive context creation with elicitation for metadata. When context metadata is not provided, this tool will elicit organizational information from the user. |
| delete_context | Delete a schema context. |
| delete_subject | 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_schema | Export a single schema in the specified format. |
| export_subject | Export all versions of a subject. |
| export_context | Export all subjects within a context. |
| export_global | Export all contexts and schemas from a registry. |
| export_global_interactive | 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_schema | Migrate a schema from one registry to another. |
| list_migrations | List all migration tasks and their status. |
| get_migration_status | Get detailed status of a specific migration. |
| migrate_context | Guide for migrating an entire context using Docker-based tools. |
| migrate_context_interactive | 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_batch | 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_batch | Clear multiple contexts in a registry using application-level batch operations. ⚠️ APPLICATION-LEVEL BATCHING: Uses individual requests per MCP 2025-06-18 compliance. |
| count_contexts | Count the number of contexts in a registry. |
| count_schemas | Count the number of schemas in a context or registry. |
| count_schema_versions | Count the number of versions for a specific schema. |
| get_registry_statistics | Get comprehensive statistics about a registry. |
| list_elicitation_requests | List all pending elicitation requests. |
| get_elicitation_request | Get details of a specific elicitation request. |
| cancel_elicitation_request | Cancel a pending elicitation request. |
| get_elicitation_status | Get the status of the elicitation system. |
| get_task_status | Get the status and progress of an async task. |
| get_task_progress | Get the progress of an async task (alias for get_task_status). |
| list_active_tasks | List all active tasks in the system. |
| cancel_task | Cancel a running task. |
| list_statistics_tasks | List all statistics-related tasks. |
| get_statistics_task_progress | Get detailed progress for a statistics task. |
| get_mcp_compliance_status_tool | 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_registry | Set the default registry. |
| get_default_registry | Get the current default registry. |
| check_readonly_mode | Check if a registry is in readonly mode. |
| get_oauth_scopes_info_tool | Get information about OAuth scopes and permissions. |
| test_oauth_discovery_endpoints | 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_tool | Get detailed information about MCP operations and their metadata. |