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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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_connectionA | 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_versionsB | 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. |
| 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_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_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_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. |
| check_compatibilityC | Check if a schema is compatible with the latest version. |
| create_contextC | Create a new schema context. |
| export_schemaC | Export a single schema in the specified format. |
| export_subjectC | Export all versions of a subject. |
| 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_mcp_compliance_status_toolA | 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. |
| get_default_registryB | Get the current default registry. |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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