MSK MCP Server

Name: MSK MCP Server
Author: yhyyz

@yhyyz

Repository

About MSK MCP Server

MSK and MirrorMaker2 on MSK connector managed through MCP server

#msk #mcp #server #kafka #amazon

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "msk-mcp-server": {
      "command": "python",
      "args": [
        "-m",
        "mcp_server_msk_mm2"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MSK MCP Server?

A Model Context Protocol server that provides management capabilities for Amazon MSK (Managed Streaming for Apache Kafka), including MirrorMaker2 connectors, custom domain creation, and disaster recovery operations. It enables LLMs to create, configure, and manage complete MSK infrastructure with DNS management and DR switching.

How to use MSK MCP Server?

Install via pip (pip install msk-mcp-server) or use uvx without installation. Configure it in Claude or VS Code by specifying the command and environment variables for AWS region, profile, or keys. Run as a script using python -m mcp_server_msk_mm2.

Key features of MSK MCP Server

Complete MirrorMaker2 pipeline orchestration with three connector types.
Custom plugin management with automatic S3 integration.
Disaster recovery switching between primary and secondary MSK clusters.
Route53 integration for custom DNS domain creation and VPC association.
Supports IAM, PLAINTEXT, and SCRAM-SHA-512 authentication.
Real-time monitoring and automated waiting for plugin and connector states.

Use cases of MSK MCP Server

Automating failover between MSK clusters across regions for disaster recovery.
Setting up cross-cluster data replication via MirrorMaker2 connectors.
Creating custom DNS domains for MSK clusters with Route53.
Monitoring and troubleshooting MSK Connect connectors and plugins.

FAQ from MSK MCP Server

What AWS permissions are required?

The server needs permissions for kafkaconnect, kafka, s3 (GetObject, PutObject, ListBucket), route53, ec2:DescribeSubnets, and ec2:DescribeVpcs.

Can it run without an existing S3 bucket?

No, an S3 bucket is required to store MirrorMaker2 plugin files, with proper IAM permissions for MSK Connect to access it.

What authentication methods does the server support?

The MirrorMaker2 module supports IAM, PLAINTEXT, and SCRAM-SHA-512 authentication for source and target clusters. The custom domain module only supports PLAINTEXT.

How do I configure environment variables?

Set AWS_REGION (default uses SDK default), AWS_PROFILE, or AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY. Optional timeouts: AWS_READ_TIMEOUT (default 300s) and AWS_CONNECT_TIMEOUT (default 60s).