How do I install the kafka schema reg mcp server?

Use a recorded configuration for your client, replace example credential values and paths, and verify the documented runtime. Restart or reconnect the client, then inspect the available tools.

What credentials does it need?

It reads `SCHEMA_REGISTRY_URL`, `SCHEMA_REGISTRY_USER`, `SCHEMA_REGISTRY_PASSWORD`, `VIEWONLY`, `SLIM_MODE`, `SCHEMA_REGISTRY_NAME_1`, `SCHEMA_REGISTRY_URL_1`, `VIEWONLY_1` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

SSyncDev

Start a project

Kafka Schema Reg MCP Server

A comprehensive **Model Context Protocol (MCP) server** that provides Claude Desktop and other MCP clients with tools for Kafka Schema Registry

Local serverstdioPython

What is the Kafka Schema Reg MCP Server?

A comprehensive Model Context Protocol (MCP) server that provides Claude Desktop and other MCP clients with tools for Kafka Schema Registry operations. Features

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

Tool	What it does
ping	Server health check
register_schema	Register new schemas
check_compatibility	Schema compatibility checking
create_context	Create new contexts
export_schema	Export single schema
export_subject	Export all subject versions
registry	//, schema://, subject:// resource URIs
list_registries	✅
get_registry_info	✅
test_registry_connection	✅
test_all_registries	✅
list_subjects	✅
get_schema	✅
get_schema_versions	✅

How to install the Kafka Schema Reg MCP Server

{
  "mcpServers": {
    "kafka-schema-reg": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "aywengo/kafka-schema-reg-mcp"],
      "env": {
        "SCHEMA_REGISTRY_URL": "your-value",
        "SCHEMA_REGISTRY_USER": "your-value",
        "SCHEMA_REGISTRY_PASSWORD": "your-value",
        "VIEWONLY": "your-value",
        "SLIM_MODE": "your-value",
        "SCHEMA_REGISTRY_NAME_1": "your-value",
        "SCHEMA_REGISTRY_URL_1": "your-value",
        "VIEWONLY_1": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

Variable	Description	Required
SCHEMA_REGISTRY_URL	Endpoint or connection string the server talks to.	Yes
SCHEMA_REGISTRY_USER	Configuration value read at startup.	Optional
SCHEMA_REGISTRY_PASSWORD	Configuration value read at startup.	Optional
VIEWONLY	Configuration value read at startup.	Optional
SLIM_MODE	Configuration value read at startup.	Optional
SCHEMA_REGISTRY_NAME_1	Configuration value read at startup.	Optional
SCHEMA_REGISTRY_URL_1	Endpoint or connection string the server talks to.	Yes
VIEWONLY_1	Configuration value read at startup.	Optional

Example prompts to try

“Use Kafka Schema Reg MCP to ping.”
“Use Kafka Schema Reg MCP to register schema.”
“Use Kafka Schema Reg MCP to check compatibility.”

Frequently asked questions

A comprehensive **Model Context Protocol (MCP) server** that provides Claude Desktop and other MCP clients with tools for Kafka Schema Registry operations. Features Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.

Alternatives to the Kafka Schema Reg MCP Server

Filesystem

Official

Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.

File Systems & StorageTypeScript★ 63.0k

Context7

Official

Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.

Documentation & API ReferencesRemoteTypeScript★ 32.0k

Ref-tools-mcp

Token efficient search for coding agents over public and private documentation.

Developer Tools

Binky

Isolated dev environments, one per git worktree: ports, env, and DB slices as agent tools.