Connect your AI client to Kite, describe what your bot should do, and it builds the commands, event listeners and messages. Kite runs the bot 24/7 for free, so there's nothing to deploy or host.
Choose whether the token can change your apps or only read them, and which apps it can use.
Add Kite to Claude Code or Codex with one command, or to Cursor, VS Code and other clients that connect to remote MCP servers.
Ask for a command or an event in plain words. The client builds the flow, Kite checks it, and it goes live in your server.
claude mcp add --transport http kite https://kite.onl/api/mcp --header "Authorization: Bearer kite_..."
Kite shows this with your token filled in when you create one.
The client sees your commands, logs, channels and roles, and looks up how each block works before it uses it.
Creates the command, the message with its buttons and a flow for each button.
Reads your app's logs, finds the block that failed and fixes its settings.
Looks up your channels and changes every flow that needs it, in one go.
Sends the requests to Discord as your bot, for things that don't need a flow.
Claude Code and Codex can write a discord.js or discord.py bot too. Then you need a server that runs it, and every change goes through the code. On Kite, the client builds flows that Kite runs, and you can open them in the editor and change them yourself.
Add verification, modmail or giveaways from the Marketplace and ask the client to change it for your server.
The bot is your own Discord application, with your name, avatar and status, not Kite's.
Kite's code is on GitHub. You can see how your bot runs, or host Kite yourself.
Each token has its own access, so a client only gets what you give it. Delete the token and the client loses access right away.
MCP, the Model Context Protocol, is a standard way for AI clients to use tools of other apps. Kite's MCP server gives clients tools to read and build your Discord bot, like listing your commands or adding a block to a flow.
Claude Code, Codex, Cursor, VS Code, OpenCode, Antigravity, Gemini CLI, Devin Desktop and other clients that connect to remote MCP servers with a token in a header. Connectors in claude.ai, the Claude app and ChatGPT need a sign-in instead, which Kite doesn't support yet.
No. Kite hosts your bot 24/7 for free, and the MCP server works on every plan without using credits or flow AI prompts. The flows it builds use credits when they run, like any other flow, and the free plan has 10,000 a month.
You can, but then you host the bot yourself and keep it running, and only someone who reads the code can change it. With Kite, the bot runs on Kite's servers for free, and anyone on your team can open what the client built in the editor and change it.
You choose what each token can do, and every change can be undone from the history. Kite tells the client to only delete or disable things you asked for. Keep the token private, because anyone who has it can control your bot.
No. Kite runs your bot 24/7. The AI client only builds and changes it, so the bot keeps running when you close the client.

Build commands by connecting blocks, or describe them and let AI build them. Kite is free to start and hosts your bot 24/7.