Kite Discord Bot Builder
Server Details
Kite is a no-code Discord bot builder that hosts your bot. Its MCP server lets your AI client build the bot for you: slash commands, event listeners and messages with buttons. It can also edit existing flows, read logs to fix errors, and add ready-made templates like tickets or verification. Changes go live right away, and commands show up in Discord within a minute.
It can also read your server through the Discord API, like channels, roles and members.
Claude, ChatGPT, Claude Code, Codex and VS Code connect by signing in. You pick which apps the client can access and whether it can make changes. Other clients like Cursor use a Kite API token. Earlier versions of every flow can be restored in Kite.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- merlinfuchs/kite
- GitHub Stars
- 330
- ChatGPT
- –
- Claude
- Kite Discord Bot Builder
TDQS
Scored across 36 tools
Most tools map to a distinct resource plus action (command, event listener, message template, variable, flow), and the search_*/get_* pairs (blocks, code calls, Discord API) are explicitly differentiated in their descriptions. The real friction is the word 'template': get_template/install_template/update_template_install/search_templates refer to marketplace templates while create_message/list_messages/get_message/update_message refer to message templates, which an agent can easily conflate. A few tools also sit near each other, e.g. set_enabled versus edit_flow/delete_command for lifecycle changes.
Nearly everything follows a clean verb_noun snake_case pattern with correct singular/plural use (get_command versus list_commands). The main deviation is discord_api_request, which is noun-only and breaks the verb-first convention, plus a couple of special-purpose names like get_flow_guide and get_usage. Overall the convention is predictable enough to guess at unseen tools.
36 tools is heavy and well above the comfortable 3-15 range, but the domain is genuinely broad (four CRUD resource families, flow editing, block catalog, Discord API proxy, marketplace, billing). Several groups still feel padded, such as the four search_*/get_* pairs and the four marketplace-template tools, which could be consolidated. It is defensible but on the excessive side.
Commands and event listeners have create/get/list/delete but no update for metadata like name or description, and stored variables only offer create and list with no update or delete, leaving obvious dead ends in the lifecycle. Message templates and the flow/edit/test surface are well covered, and the block, code-call and Discord API discovery tools round things out. The gaps are notable but mostly workable around.
Publisher details
- Operator
- Not applicable
- Operator website
- https://kite.onl · Publisher source
- Vendor relationship
- Not available
- Documentation
- https://docs.kite.onl/guides/mcp · Publisher source
- Privacy policy
- Not provided
- Trust center
- Not available
- Restrictions
- Not available
Available Tools
36 toolscreate_commandCreate commandAInspect
Creates a slash command, optionally with edits that build its flow. A subcommand is its own command named like 'mod ban'. Discord shows new commands within a minute.
Inputs: name (required), app_id (required), description (required), edits, +1 more.
create_event_listenerCreate event listenerAInspect
Creates an event listener, optionally with edits that build its flow. It runs on a Discord event, on a schedule (cron) or on requests to its webhook URL (webhook). The Discord events:
message_create: A message is sent.
direct_message_create: A user sends your bot a direct message. Message create, update, and delete only run for messages in servers.
message_update: A message is edited.
message_delete: A message is deleted.
message_reaction_add: A reaction is added to a message.
message_reaction_remove: A reaction is removed from a message.
guild_member_add: A member joins the server. Needs the Server Members Intent.
guild_member_remove: A member leaves the server. Needs the Server Members Intent.
guild_boost: A member boosts the server. Boosts are detected from the message Discord posts when someone boosts the server. The server needs a system messages channel with boost messages enabled, and your bot needs to see it.
guild_boost_remove: A member stops boosting the server. Needs the Server Members Intent. Detected when Discord takes the Server Booster role away, which happens once the member's last boost ends. Only works for members your bot has seen since it last started, like by sending a message, joining or being updated.
guild_audit_log_entry_create: Something is logged in the server's audit log. Runs for bans, kicks, timeouts, role changes, channel changes and more. Your bot needs the View Audit Log permission in the server. Pick the actions with an Event Filter.
voice_state_update: A member joins, leaves, or moves voice channels.
guild_create: Your bot is added to a server.
guild_delete: Your bot is removed from a server.
Inputs: app_id (required), event_type (required), description (required), cron, +2 more.
create_messageCreate message templateAInspect
Creates a message template, which flows can send. Its buttons and select menus get a flow_source_id, use it with edit_flow to build what they do.
Inputs: data (required), name (required), app_id (required), description.
create_variableCreate stored variableAInspect
Creates a stored variable, which keeps a value between runs, for blocks with a variable_id setting.
Inputs: name (required), app_id (required), scoped (required).
delete_commandDelete commandBDestructiveInspect
Deletes a command. Only do this when the user asked for it.
Inputs: app_id (required), command_id (required).
delete_event_listenerDelete event listenerBDestructiveInspect
Deletes a event listener. Only do this when the user asked for it.
Inputs: app_id (required), event_listener_id (required).
delete_messageDelete message templateBDestructiveInspect
Deletes a message template. Only do this when the user asked for it.
Inputs: app_id (required), message_id (required).
discord_api_requestDiscord API requestADestructiveInspect
Sends a request to an endpoint of the Discord API with the bot token of an app, like Discord's API docs describe, and returns the JSON it returns. Find the endpoint with search_discord_api first. The bot can only do what its roles allow in a server. Changes happen right away and can't be undone, so only make the ones the user asked for. They're logged in the app's logs and the server's audit log. Big results are shortened to the first items of their lists and the start of long strings, and returned as {"truncated": true, "result": ...}. Use the endpoints the result names, or limit and pagination parameters, for the rest. Never send a shortened list or string back to Discord, like the permission overwrites of a channel, as the left out items would be deleted. Get it in full first.
Inputs: app_id (required), operation (required), body, query, +2 more.
edit_flowEdit flowADestructiveInspect
Edits the flow of a command, an event listener, or a button or select menu of a message template, and saves it. Pass one of command_id, event_listener_id or message_id. If an edit or the resulting flow has problems, nothing is saved and the problems are returned.
Inputs: edits (required), app_id (required), command_id, message_id, +2 more.
get_blocksGet blocksARead-onlyInspect
Gets block types: what each does, where it can be used, its outputs, the JSON Schema of its settings and of its result. Get all the types you need in one call.
Inputs: types (required).
get_code_callsGet code callsBRead-onlyInspect
Gets calls the code of a Run JavaScript block can make as TypeScript: what each does and costs, and the parameters of the one object it takes. Calls return promises. types declares the Discord objects they take and return, and the discord types those use are the objects of Discord's API with the same name.
Inputs: names (required).
get_commandGet commandARead-onlyInspect
Gets a slash command of an app with its flow.
Inputs: app_id (required), command_id (required).
get_event_listenerGet event listenerCRead-onlyInspect
Gets an event listener of an app with its flow.
Inputs: app_id (required), event_listener_id (required).
get_flow_guideGet flow guideARead-onlyInspect
Explains how to build flows: the edits, buttons and select menus, message templates, placeholders and rules. Call it once before creating or editing a flow.
Inputs: no named parameters.
get_messageGet message templateBRead-onlyInspect
Gets a message template of an app: its content, and the flow of each button and select menu by its flow_source_id.
Inputs: app_id (required), message_id (required).
get_templateGet templateARead-onlyInspect
Gets a template: what it adds, the parameters to fill in when adding it, like a channel, and the integrations it needs. With app_id, also what the app has of it already and what updating it would change.
Inputs: template_id (required), app_id.
get_usageGet credit usageARead-onlyInspect
Gets the credits an app used this month, how many its plan has per month, and the credits used each day and by commands, event listeners, scheduled tasks, webhooks, and messages. Credits reset at the start of each month in UTC, and an app that uses all of them stops running flows until then. get_blocks says what each block costs, and list_plans what other plans include.
Inputs: app_id (required).
install_templateAdd templateAInspect
Adds a template to an app: its commands, event listeners, messages and stored variables, with the parameters filled in. Messages the template posts in a channel are posted right away. Templates not made by Kite are made by other users, so tell the user who made it and ask before adding one. Get the template with get_template and app_id first, and ask the user for the parameters you can't pick from list_channels and list_roles. When the app has a command with the same name, the template's command gets a number, like /giveaway-2, so tell the user the names the result has.
Inputs: app_id (required), template_id (required), items, messages, +2 more.
list_appsList appsBRead-onlyInspect
Lists the apps of the user, the Discord bots they build.
Inputs: no named parameters.
list_channelsList channelsCRead-onlyInspect
Lists the channels of a Discord server the app's bot is in. type is Discord's channel type, like 0 for text and 4 for categories.
Inputs: app_id (required), server_id (required).
list_commandsList commandsARead-onlyInspect
Lists the slash commands of an app, without their flows. Each command and subcommand, like /mod ban, is its own command with its own flow.
Inputs: app_id (required).
list_event_listenersList event listenersARead-onlyInspect
Lists the event listeners of an app, without their flows. They run on Discord events, on a schedule or on requests to a webhook URL.
Inputs: app_id (required).
list_logsList logsARead-onlyInspect
Lists the newest log entries of an app, like errors of flows, optionally only those of one command, event listener or message template.
Inputs: app_id (required), limit, command_id, message_id, +1 more.
list_messagesList message templatesARead-onlyInspect
Lists the message templates of an app. Flows send them, and their buttons and select menus run flows of their own.
Inputs: app_id (required).
list_plansList plansARead-onlyInspect
Lists Kite's plans with their prices in USD and limits, like credits per month, and the page where the user can change the plan of an app. Only bring plans up when the app is near a limit or the user asks, and first suggest ways to need less, like a smaller AI model tier.
Inputs: app_id (required).
list_rolesList rolesBRead-onlyInspect
Lists the roles of a Discord server the app's bot is in, highest first. Managed roles belong to bots and integrations.
Inputs: app_id (required), server_id (required).
list_serversList serversARead-onlyInspect
Lists the Discord servers the app's bot is in.
Inputs: app_id (required).
list_variablesList stored variablesBRead-onlyInspect
Lists the stored variables of an app, which keep values between runs. Scoped ones keep a value per scope, like per user.
Inputs: app_id (required).
search_blocksSearch blocksARead-onlyInspect
Searches the block types flows are built from by words in their type, title or description. Without words it lists all of them by title only.
Inputs: query, context.
search_code_callsSearch code callsARead-onlyInspect
Searches the calls the code of a Run JavaScript block (action_javascript_run) can make, like discord.getChannel, variables.get or http.request, by words in their name or description. Without words it lists all of them by name only.
Inputs: query.
search_discord_apiSearch Discord APIARead-onlyInspect
Finds endpoints of the Discord API that discord_api_request can call, by words of their name or path, like "member role" or "channels messages". Names are operation IDs of Discord's OpenAPI spec, like update_guild for Modify Guild.
Inputs: query (required).
search_templatesSearch templatesARead-onlyInspect
Searches the templates of the marketplace, made by Kite or by users, and the user's own ones. A template adds commands, event listeners and messages to an app, which is quicker than building them. Without words it lists all of them.
Inputs: query.
set_enabledEnable or disableADestructiveIdempotentInspect
Enables or disables a command or an event listener. Pass one of command_id or event_listener_id.
Inputs: app_id (required), enabled (required), command_id, event_listener_id.
test_flowTest flowARead-onlyInspect
Runs a flow as a test without changing anything, to check that it does what it should. The flow runs with a fake trigger: the command with the options, the event of an event listener, a webhook request, or a click on a button or select menu of a message template. Reads from Discord are real, like members and roles. Nothing is sent or changed: messages, role changes and every other change are returned as effects of their block, with warnings when Discord would reject them, like a missing permission or a role above the bot's. Stored variables are read, and changes to them only last for the test. Use variables to start the test with other stored values, like a balance, XP or the time a cooldown started. Blocks that call services other than Discord, like Send API Request, AI and integrations, don't run and have no result unless you mock them. Mock blocks to test each branch, like the error branch of an Error Handler or the answers of AI Check and AI Choice. Waits are skipped. Use then to click the buttons, use the select menus and submit the modals the flow showed, which runs those parts of the flow. Returns each run of the flow with the blocks that ran in order, their results, errors and effects. After building or changing a flow, test the branches that matter and fix what fails before telling the user it works.
Inputs: app_id (required), dm, then, event, +12 more.
update_messageUpdate message templateADestructiveInspect
Changes the name, description or content of a message template. data replaces the whole message, so start from get_message. Keep the flow_source_id of existing buttons and select menus, or their flows are deleted.
Inputs: app_id (required), message_id (required), data, name, +2 more.
update_template_installUpdate templateADestructiveInspect
Updates what an app has of a template to the template's newest version. Items the user didn't edit are replaced, edited ones only if they're in overwrite, which loses the user's changes, so ask first. get_template with app_id shows what an update changes.
Inputs: app_id (required), template_id (required), overwrite, parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Build and change Discord bots by describing them: slash commands, events, embeds, modals and data.
Discord MCP server for ChatGPT, Claude and any AI agent: list servers and channels, read channel messages, search messages, send message, reply to message, send DM, read mentions and assign role in your own Discord account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Discord yourself; Cotlet does not store your password and you need no Discord API key. About the official Discord API: Yes, Discord has an official API for bots and OAuth2 apps, but it acts as a bot that a server manager adds, not as you, and Discord has no official MCP server for it (checked 5 Nov 2026). The MCP server on Discord's docs site only searches documentation. Setup and FAQ: https://cotlet.dev/integrations/discord-api-mcp-server
Build Discord communities with AI: roles, channels, modules, automations and reviewed announcements.
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
Related MCP Servers
- AlicenseBqualityCmaintenanceConnects AI assistants to a user's own Discord bot over MCP stdio, letting them manage server design, channels, roles, messages, voice, moderation, community events, and webhooks through the official Discord API using natural language. Runs locally with a bot token, requires no custom bot commands, and restricts actions by the bot's granted permissions and an optional server allowlist.271MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude, Cursor, or Codex to build and manage Discord servers end to end — creating channels, roles, permission overwrites, threads, webhooks, events, and messages, plus whole-server blueprints applied idempotently. Includes guard rails like read-only and safe modes, per-server allowlists, and permission explanations.141 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI apps to create and modify Discord bot drafts, including flows, embeds, modals, buttons, variables, and collections, through remote MCP tools with OAuth sign-in. Changes remain in the draft for review and deployment in the builder.MIT

Familiarofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate self-hosted Discord bots with per-session active identity and per-call overrides, covering messages, channels, threads, members, roles, moderation, automod, webhooks, events, and raw REST passthrough. Supports scoped keys with read-only and category ceilings, confirmation-gated destructive actions, and encrypted token storage.1AGPL 3.0
Glama MCP Gateway
Add one secure layer between your agents and this server.