AgentSidekick

Better agent tooling for Apache Kafka

Integration gap · Measured demandOverall 42.3 / 100 DERConfidence Low DERCalculated

20 public GitHub issues mention "Apache Kafka mcp" (checked 2026-11-21) SRC, while 27 indexed products mention Apache Kafka DER. On the six weighted components it scores 42.3 of 100, confidence Low, as of 2026-11-21.

Score breakdown

Contribution = weight × component score. The contributions add up to the overall score.

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.250.00.25 × 0.0 = 0.00Measured
Competition gap0.2055.00.20 × 55.0 = 11.00Measured
Monetisation0.2055.00.20 × 55.0 = 11.00Heuristic
Growth (relative)0.1529.00.15 × 29.0 = 4.35Measured
Feasibility0.1080.00.10 × 80.0 = 8.00Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0042.25 → 42.3

Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.

Confidence: Low

Rule: Medium when at least 50 GitHub issues mention the integration and at least 10 indexed products mention it; otherwise Low. Nothing is rated High.

What would raise it

  • At least 50 GitHub issue mentions (now 20).

The opportunity

All text in this section is generated by rule from the record. It is a starting point, not research.

Description
Developers are asking for Apache Kafka access from AI agents more than the current supply of well-maintained tools would suggest.DER
Problem
Agents need to read from and act on Apache Kafka. Only some of the existing tools are both documented and actively maintained.DER
Target users
Developers and individuals who use Apache KafkaHEU
Product form
MCP server (optionally bundled as a plugin with skills)HEU
Revenue model
Open source with paid hosting or supportHEU
Complexity
Low to mediumHEU
Competition level
HighDER
Subject
Apache Kafka (integration)

Evidence for

3 row(s) from opportunity_evidence.

  • Competition gapMeasuredDERvalue 18

    27 indexed products mention Apache Kafka; 18 of them have a complete record and a repository pushed in the last 180 days.

    /integrations/kafka/

  • FeasibilityHeuristicHEU

    Apache Kafka has a public API (documentation linked).

    Source

  • DistributionMeasuredDERvalue 37

    37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.

    /platforms/

Evidence against

4 row(s) from opportunity_evidence.

  • DemandMeasuredDERvalue 20

    20 public GitHub issues contain the phrase "Apache Kafka mcp" (checked 2026-11-21); that is the 0th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.

    Source

  • MonetisationHeuristicHEU

    Apache Kafka is not primarily a paid business product; "data-warehouse" tooling is a category companies commonly pay for. This is a rule of thumb, not revenue data.

  • Growth (relative)MeasuredDERvalue 13

    13 products launched in the last 90 days versus 6 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.

  • Competition gapMeasuredDER

    One project holds 98% of the 12,448 GitHub stars in this segment, so there is an established leader to displace.

Existing products

All Apache Kafka products

The most notable profiled products mentioning Apache Kafka (up to 8). 27 indexed in total.

mcp

MCP serverby kubesharkSRC

12k GitHub starspushed 11d agoApache-2.0

strimzi-kafka-cli

MCP serverby SystemCraftsmanSRC

91 GitHub starspushed 3mo agoApache-2.0

streaming-skills-plugin

Pluginby confluentincSRC

66 GitHub starspushed 10d agoApache-2.0

Aiven MCP

MCP serverby aiven.ioSRC

28 GitHub starspushed 1d agoApache-2.0

orion

MCP serverby GoPlasmaticSRC

10 GitHub starspushed 4d agoApache-2.0

Infrawise

MCP serverby Sidd27SRC

22 GitHub starspushed 1d agoMIT

Conduktor

MCP serverby conduktorSRC

5 GitHub starspushed 1mo agoApache-2.0

Where it could be distributed

All platforms

37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.

ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more

Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU

Data coverage

Indexed products
27DER
With a full profile
8+DER
Launches, last 90 days
13 vs 6 in the 90 beforeSRC
Demand measured
SRC
Segment calculated
Score calculated

Risks and counterarguments

  • The vendor may ship (or already ships) an official Apache Kafka server, which usually becomes the default.
  • Issue mentions measure developer discussion, not willingness to pay.
  • 20 public GitHub issues contain the phrase "Apache Kafka mcp" (checked 2026-11-21); that is the 0th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.
  • Apache Kafka is not primarily a paid business product; "data-warehouse" tooling is a category companies commonly pay for. This is a rule of thumb, not revenue data.
  • 13 products launched in the last 90 days versus 6 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.
  • One project holds 98% of the 12,448 GitHub stars in this segment, so there is an established leader to displace.

Assumptions

What has to be true for the score to mean anything.

  • Mentions of "Apache Kafka mcp" in GitHub issues reflect developers wanting Apache Kafka access from agents.
  • Products that mention the integration in their description or package metadata are the competing supply; ones that do not name it are missed.
  • "Well-maintained" means data completeness ≥ 0.6 and a repository push in the last 180 days.
  • Percentiles compare this integration only with the other integrations tracked, not with the wider market.
  • A platform that documents MCP support can run any MCP server; no pairing has been tested.

How to verify this yourself

  1. Run the demand query on GitHub: https://github.com/search?q=%22Apache%20Kafka%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 20 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
  2. Check the supply on the Apache Kafka page and search the official MCP Registry and the vendor's own app directory for an official server.
  3. Download the record with all evidence: /api/dataset/opportunities.json.

All opportunities · Methodology · Report an error

Page data last updated .