MCP.Market

nifi-clickhouse-kafka-mcp server

by arogan178·io.github.arogan178/nifi-clickhouse-kafka-mcp·v0.1.0
No reviews yet

Read-only Apache NiFi, ClickHouse and Kafka access with OIDC, audit and secret masking

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars66 downloads/wk

Reviews

Write one

Nobody has reviewed nifi-clickhouse-kafka-mcp yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

nifi-clickhouse-kafka-mcp tools (29, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • clickhouse_databases

    Databases with their engine, table count and total size.

  • clickhouse_describe_table

    Columns (name, type, default, comment) plus engine, sorting, primary and partition keys and size of a table.

  • clickhouse_health

    Server health in one call: version and uptime, replicas with problems, disk use, partitions with the most active parts, longest running queries, merges, unfinished mutations and errors in the last hour.

  • clickhouse_querywrite action

    Run one read-only ClickHouse statement (SELECT, WITH, SHOW, DESCRIBE, EXISTS, EXPLAIN).

  • clickhouse_search_columns

    Find columns whose name or comment contains a string (case-insensitive), across all user tables.

  • clickhouse_tables

    Tables and views with engine, rows, size and comment, sorted by database and name.

  • environments

    The environments this server can read, with their description and which systems each one has.

  • kafka_cluster

    Brokers, controller, topic and partition counts, and under-replicated or offline partitions.

  • kafka_consumer_groups

    List consumer groups (id and state) sorted by id, optionally filtered by a substring.

  • kafka_consumer_lag

    Committed offsets and lag per partition for an existing consumer group (see kafka_consumer_groups).

  • kafka_describe_topic

    Partitions with earliest/latest offsets and non-default configs of a Kafka topic.

  • kafka_sample

    Read up to 50 messages from one partition without joining any consumer group.

  • kafka_search

    Scan all partitions of a topic for messages matching every given filter, without joining a group.

  • kafka_topics

    List Kafka topics sorted by name, optionally filtered by a substring.

  • nifi_bulletins

    Recent NiFi bulletins (warnings and errors), optionally for one component.

  • nifi_component

    Full configuration of one NiFi component, without property descriptors.

  • nifi_controller_services

    Controller services of a process group and its ancestors, with their state.

  • nifi_flow_tree

    Process group hierarchy with ids, queued data and processor counts by state, down to depth levels.

  • nifi_flowfile

    Attributes of one queued FlowFile (see nifi_queue), optionally with content[offset:offset+length].

  • nifi_health

    Problems in a flow in one call, worst first.

  • nifi_parameter

    One NiFi parameter's value, value[offset:offset+length]; next_offset is None at the end.

  • nifi_parameters

    Parameters of all readable NiFi parameter contexts, sorted by context and name.

  • nifi_process_group

    Contents of a process group: child groups, processors, connections with queue sizes, ports.

  • nifi_processor_state

    Stored state of a processor, e.g. the last listed timestamp or maximum column values.

  • nifi_provenance

    Search NiFi provenance events of a component (processor, port, ...) and/or a FlowFile.

  • nifi_provenance_event

    One provenance event (see nifi_provenance) with attributes, previous values that changed, and content.

  • nifi_queue

    FlowFiles at the head of a connection's queue (NiFi lists at most 100), with total queue size.

  • nifi_search

    Search the NiFi flow for components by name, id, property or type.

  • nifi_status

    NiFi version, controller status (threads, queued data, component counts) and cluster node summary.

Public scan report

scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan17 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How nifi-clickhouse-kafka-mcp compares

Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 802 Databases servers
Tools
29
the typical Databases server has 8
Tools that change things
3%
typical: 10%. Fewer write tools means less an agent can break
Downloads a week
66
more than 48% of 324 Databases servers with a package

What its tools let an agent do: 28 read · 1 change

Install nifi-clickhouse-kafka-mcp in Claude Code, Cursor or VS Code

claude mcp add nifi-clickhouse-kafka-mcp -- uvx nifi-clickhouse-kafka-mcp
Add to Cursor

What the publisher says

From the nifi-clickhouse-kafka-mcp repository's README, as published. We do not edit it. Read it on GitHub

nifi-clickhouse-kafka-mcp

<!-- mcp-name: io.github.arogan178/nifi-clickhouse-kafka-mcp -->

A read-only MCP server that lets AI assistants look inside Apache NiFi, ClickHouse and Kafka: one server, every environment, and nothing it can break.

Ask Claude, Cursor or any MCP client things like:

error bulletin, worst first.

  • "Why is the orders flow in prod backed up?" → nifi_health finds the full queue, the stopped processor and the
  • "Show me a FlowFile stuck in that queue and where it came from." → nifiqueue, nififlowfile, nifi_provenance.
  • "Is the billing consumer losing data?" → kafkaconsumerlag flags partitions already behind retention.
  • "Find the message for order 42 sent in the last hour." → kafka_search by key, substring or JSON field.
  • "Which tables have customer data and how big are they?" → clickhousesearchcolumns, clickhousedescribetable.

It grew out of a gateway built to give a data platform team AI access to NiFi 2, ClickHouse and Strimzi Kafka clusters without handing out credentials or write access.

How it works

flowchart LR
    clients["MCP clients<br/>Claude Code, Claude Desktop,<br/>Cursor, VS Code, ..."]
    idp["OIDC provider<br/>Keycloak, Entra ID, Okta, ..."]
    gw["<b>nifi-clickhouse-kafka-mcp</b><br/>lock 1<br/>───<br/>token + group check<br/>read-only tools<br/>request allowlist<br/>SQL parse check<br/>masking, size caps<br/>audit, metrics"]
    subgraph backends["Lock 2: read-only identities"]
        nifi["NiFi<br/>view-only policies"]
        ch["ClickHouse<br/>readonly user, SELECT grants"]
        kafka["Kafka<br/>Read/Describe ACLs"]
    end
    clients -- "stdio, or HTTP<br/>+ bearer token" --> gw
    clients -. "log in" .-> idp
    gw -. "verify token" .-> idp
    gw --> nifi
    gw --> ch
    gw --> kafka

Each environment (prod, staging, ...) has its own set of backends; one server serves them all.

Why this one

See docs/landscape.md for how this compares with other NiFi, ClickHouse and Kafka MCP servers and which of their users' complaints it answers.

Quick start

Try it against a local NiFi 2, ClickHouse and Kafka:

git clone https://github.com/arogan178/nifi-clickhouse-kafka-mcp && cd nifi-clickhouse-kafka-mcp/examples/demo
docker compose up -d          # NiFi takes about a minute
uv run --with requests python seed_nifi.py
claude mcp add data -- uvx nifi-clickhouse-kafka-mcp --config "$PWD/config.yaml"

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

nifi-clickhouse-kafka-mcp: common questions

Is nifi-clickhouse-kafka-mcp server safe?
Yes, by our scan: it is graded A (92/100). Read the nifi-clickhouse-kafka-mcp safety report
How do I install nifi-clickhouse-kafka-mcp?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does nifi-clickhouse-kafka-mcp need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is nifi-clickhouse-kafka-mcp maintained?
The last commit was 14 days ago (2026-10-19). The latest release is v0.1.0.
What can I use instead of nifi-clickhouse-kafka-mcp?
Servers from other publishers that do the same job: Midplane MCP server, ClickHouse MCP server and Kubeshark MCP server.
How does nifi-clickhouse-kafka-mcp compare with other Databases MCP servers?
safety score 92/100 (higher than 90% of 802 Databases servers); tools 29 (the typical Databases server has 8); tools that change things 3% (typical: 10%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to nifi-clickhouse-kafka-mcp

Same job from other publishers: the closest match first, then the best rated.

  • Midplane
    A gateway between AI agents and Postgres: table access, masking at the source, approvals and audit.
    B
  • ClickHouse
    Official ClickHouse MCP server for querying and exploring ClickHouse clusters and chDB.
    A
  • Kubeshark
    Real-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.
    A
  • Infrawise
    Live AWS, database & Kafka infrastructure context for AI coding assistants via MCP.
    A
  • Januscope
    Local MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.
    A