Skip to main content
Glama

mcp-confluent

Official
by confluentinc
delete-topics-handler.ts•1.26 kB
import { ClientManager } from "@src/confluent/client-manager.js"; import { CallToolResult } from "@src/confluent/schema.js"; import { BaseToolHandler, ToolConfig, } from "@src/confluent/tools/base-tools.js"; import { ToolName } from "@src/confluent/tools/tool-name.js"; import { EnvVar } from "@src/env-schema.js"; import { z } from "zod"; const deleteKafkaTopicsArguments = z.object({ topicNames: z .array(z.string().describe("Names of kafka topics to delete")) .nonempty(), }); export class DeleteTopicsHandler extends BaseToolHandler { async handle( clientManager: ClientManager, toolArguments: Record<string, unknown>, ): Promise<CallToolResult> { const { topicNames } = deleteKafkaTopicsArguments.parse(toolArguments); await ( await clientManager.getAdminClient() ).deleteTopics({ topics: topicNames }); return this.createResponse(`Deleted Kafka topics: ${topicNames.join(",")}`); } getToolConfig(): ToolConfig { return { name: ToolName.DELETE_TOPICS, description: "Delete the topic with the given names.", inputSchema: deleteKafkaTopicsArguments.shape, }; } getRequiredEnvVars(): EnvVar[] { return ["KAFKA_API_KEY", "KAFKA_API_SECRET", "BOOTSTRAP_SERVERS"]; } }

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/confluentinc/mcp-confluent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server