Start a multi-step workflow for complex Schema Registry operations

List available multi-step workflows

Get the status of active workflows

Abort an active workflow

Get detailed information about a workflow definition

Start the Schema Evolution Assistant workflow. This guided workflow helps you safely evolve schemas by analyzing changes, suggesting strategies, and coordinating consumer updates.

Start the Schema Migration Wizard workflow for guided schema migration

Start the Context Reorganization workflow for reorganizing schemas across contexts

Start the Disaster Recovery Setup workflow for configuring DR strategies

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 two Schema Registry instances and show differences.

Compare contexts across two registries.

Find schemas that exist in source registry but not in target registry.

List all available MCP resources and their usage patterns.

Suggest the appropriate resource to use instead of a removed tool.

Generate resource URI templates for your specific configuration.

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 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 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 connections to all configured registries.

NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://status' resource instead for better performance.

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 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 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 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 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 configuration settings.

NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://{name}/config' resource instead for better performance.

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 all available schema contexts.

NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://{name}/contexts' resource instead for better performance.

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 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 a new schema version.

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 if a schema is compatible with the latest version.

Interactive compatibility checking with elicitation for resolution options.

When compatibility issues are found, this tool will elicit resolution preferences from the user.

Update global configuration settings.

Update configuration settings for a specific subject.

Update the mode of the Schema Registry.

Update the mode for a specific subject.

Create a new schema context.

Interactive context creation with elicitation for metadata.

When context metadata is not provided, this tool will elicit organizational information from the user.

Delete a schema context.

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 a single schema in the specified format.

Export all versions of a subject.

Export all subjects within a context.

Export all contexts and schemas from a registry.

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 a schema from one registry to another.

List all migration tasks and their status.

Get detailed status of a specific migration.

Guide for migrating an entire context using Docker-based tools.

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 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 in a registry using application-level batch operations.

⚠️ APPLICATION-LEVEL BATCHING: Uses individual requests per MCP 2025-06-18 compliance.

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.

Update schemas in bulk with interactive guidance.

Supports compatibility settings, naming conventions, and metadata updates. Pattern matching supported (e.g., test-, deprecated-).

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.

Migrate schemas between contexts or registries.

Supports pattern-based selection and maintains schema IDs. Includes preview and rollback capabilities.

Update configuration settings across multiple schemas or contexts.

Supports security policies, retention settings, and access controls.

Count the number of contexts in a registry.

Count the number of schemas in a context or registry.

Count the number of versions for a specific schema.

Get comprehensive statistics about a registry.

List all pending elicitation requests.

Get details of a specific elicitation request.

Cancel a pending elicitation request.

Get the status of the elicitation system.

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 all available multi-step workflows for complex operations.

Get the status of active workflows.

Get the status and progress of an async task.

Get the progress of an async task (alias for get_task_status).

List all active tasks in the system.

Cancel a running task.

List all statistics-related tasks.

Get detailed progress for a statistics task.

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 the default registry.

Get the current default registry.

Get information about OAuth scopes and permissions.

Test OAuth discovery endpoints to ensure proper MCP client compatibility.

Validates:

• /.well-known/oauth-authorization-server

• /.well-known/oauth-protected-resource

• /.well-known/jwks.json

Args: server_url: Base URL of the MCP server (default: http://localhost:8000)

Returns: Dictionary with test results for each discovery endpoint

Get detailed information about MCP operations and their metadata.