Kafka MCP

Overview Schema Source Related Servers Discussions Admin

commit_offset

Move Kafka consumer group offsets for up to 1,000 group-topic targets in one call by exact offset, timestamp, or earliest/latest position; preview skipped or replayed messages before confirming.

Instructions

Move 1 to 1000 consumer group positions in one call through items. Each item names a group and topic and exactly one target: offset (one partition, the next offset the group reads), timestamp (RFC3339; each partition moves to its first message at or after that time, which is how messages are replayed since a moment), or position (earliest or latest). With timestamp or position, omit partition to move every partition of the topic. Moving one offset is an items array of length one.

The response previews, per partition and in total, how many messages each move would skip or replay. No change is made unless confirm is true; one confirm covers the whole batch, and applying is not atomic because Kafka cannot roll back commits that succeeded before a later item failed. Results follow items order, each carrying index with result or error.

Active groups are refused unless allow_active_members is set on the item, because running consumers may overwrite the commit. Requires Kafka offset-commit permission.

Input Schema

Name	Required	Description	Default
`items`	Yes	The moves to make, 1 to 1000 of them. Moving one offset is an array of length one. Two items that would move the same group, topic and partition, including a whole-topic item and a partition item, are refused before anything changes.
`confirm`	No	Optional. When false or omitted, nothing is changed and the response describes what would happen for every item. Must be true to actually move the offsets. One confirm covers the whole batch.

Output Schema

Name	Required	Description	Default
`atomic`	Yes
`failed`	Yes
`applied`	Yes
`results`	Yes
`succeeded`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.7Oct 25, 2026

changedInput schema / properties / items / description

Previous value: -"The moves to make, 1 to 100 of them. Moving one offset is an array of length one. Two items that would move the same group, topic and partition, including a whole-topic item and a partition item, are refused before anything changes."New value: +"The moves to make, 1 to 1000 of them. Moving one offset is an array of length one. Two items that would move the same group, topic and partition, including a whole-topic item and a partition item, are refused before anything changes."

First observedv0.2.0Oct 7, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so: it is a dry-run by default ('No change is made unless confirm is true'), one confirm covers the whole batch, applying is non-atomic and earlier commits cannot be rolled back, results follow items order with index, active groups are refused for a stated reason, and Kafka offset-commit permission is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the three targets, then the safety/confirmation behavior, then the active-group caveat. Slight redundancy with the schema in the parameter enumeration, but each paragraph carries distinct operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return shape needn't be spelled out, yet the description still signals the preview (per-partition and total skipped/replayed counts), the confirm gate, and the per-item result/error structure. Nothing an agent needs to invoke this mutation correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, and most of the description's parameter detail (offset meaning, timestamp semantics, position values, allow_active_members rationale) restates what the schema already documents. It adds only marginal framing, like 'Moving one offset is an items array of length one' and the exactly-one-target rule.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: 'Move 1 to 1000 consumer group positions in one call through items.' No sibling tool (describe_consumer_group, delete_consumer_group, consumer_lag) does offset mutation, and the batch/replay framing makes the domain unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains precisely which of the three mutually exclusive targets to use and under what conditions: offset for a single partition, timestamp 'to replay since a moment', position for earliest/latest, and omit partition to move all partitions. It also describes the single-item case. It stops short of naming sibling alternatives such as describe_consumer_group for inspection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.