# KickBot API and MCP

> The KickBot REST API and MCP server let AI apps, agents and your own scripts read and change your KickBot settings, the same way you do in the dashboard.

Source: https://kickbot.com/docs/api

KickBot has a REST API at `https://kickbot.com/api/v1` and an MCP server at `https://kickbot.com/api/v1/mcp`. With them, an AI app (ChatGPT, Claude, Grok, Cursor and others) or your own code can set up and run what you manage in the dashboard: custom commands, timed messages, TTS, chat alerts, overlays, widgets, tipping, clips, VODs and more. You create keys and connect apps on the **API & MCP** page of the dashboard.

You need a KickBot account with your Kick channel connected. See [Create your KickBot account](https://kickbot.com/docs/getting-started/create-your-account).

> **Note:** The API is free on every plan. Your plan limits are the same in the API as in the dashboard. For example, on the Free plan up to 5 custom commands can be on at the same time.

## Two ways to connect

| | Best for | How it signs in |
|---|---|---|
| **MCP server** `https://kickbot.com/api/v1/mcp` | AI chat apps and agents | **Connect to KickBot** (you approve the app in your browser), or an API key |
| **REST API** `https://kickbot.com/api/v1` | Your own scripts and bots | An API key, sent as `Authorization: Bearer kb_live_...` |

Both give the same actions. Every MCP tool is also a REST endpoint with the same name.

## What the API can and cannot do

- It can do what you can do on the dashboard pages it covers, with **your** team permissions on that channel.
- It cannot send a chat message directly. KickBot posts in chat only through what you set up (commands, timed messages, chat alerts and so on).
- It uses the same limits as the dashboard: plan limits and field limits (for example, 500 characters for a command reply).
- It cannot see or change billing, payouts, refunds, the Stripe setup, referrals or your team members. It never shows the tip widget URL or other secret keys.
- Every change an app or key makes shows in **Recent API activity** on the **API & MCP** page.

## Get started

1. [Quickstart with the REST API](https://kickbot.com/docs/api/start/quickstart): your first calls with `curl`.
2. [Create and use API keys](https://kickbot.com/docs/api/start/api-keys): keys for scripts and agents.
3. [Connect an AI app](https://kickbot.com/docs/api/start/connect-ai-apps): ChatGPT, Claude, Grok, Cursor and other MCP apps.
4. [Build your own agent](https://kickbot.com/docs/api/start/build-an-agent): point an agent framework at the MCP server.
5. [Permissions and security](https://kickbot.com/docs/api/start/permissions-and-security): what a key or app can do, the activity log, and OAuth details.
6. [Errors and limits](https://kickbot.com/docs/api/start/errors-and-limits): error codes and rate limits.

## API reference

The reference has one page per area. Each page lists every action with its REST path, its access (read or write) and all of its fields. The area names are the same as in the dashboard sidebar.

| Area | MCP area name | What it covers |
|---|---|---|
| [Account](https://kickbot.com/docs/api/reference/account) | `account` | Channel overview, plan limits, activity, Kick data refresh, moderator check |
| [Custom commands](https://kickbot.com/docs/api/reference/commands) | `commands` | Chat commands that reply with a set message |
| [Timed messages](https://kickbot.com/docs/api/reference/timers) | `timers` | Messages KickBot posts in chat on an interval |
| [Clip command](https://kickbot.com/docs/api/reference/clip-command) | `clip_command` | The `!clip` command and the clips it makes |
| [Moderation](https://kickbot.com/docs/api/reference/moderation) | `moderation` | Chat filters and moderation logs |
| [AI character](https://kickbot.com/docs/api/reference/ai-character) | `ai_character` | The AI chat character |
| [AI images (Imagine)](https://kickbot.com/docs/api/reference/imagine) | `imagine` | The `!imagine` command and its widget |
| [Chat alerts](https://kickbot.com/docs/api/reference/chat-alerts) | `chat_alerts` | Chat messages for subs, gifted subs, follows and KICKs |
| [Text-to-speech](https://kickbot.com/docs/api/reference/tts) | `tts` | TTS settings, voices, auto read, moderation, queue, voice clones |
| [Tipping](https://kickbot.com/docs/api/reference/tipping) | `tipping` | Tip page, tip widget, tip moderation, queue, earnings |
| [Overlay widgets](https://kickbot.com/docs/api/reference/overlays) | `overlays` | The built-in (legacy) overlays |
| [Custom widgets](https://kickbot.com/docs/api/reference/widgets) | `widgets` | Widget builder, widget library, installed widgets |
| [Clips](https://kickbot.com/docs/api/reference/clips) | `clips` | Kick clip downloads |
| [VODs](https://kickbot.com/docs/api/reference/vods) | `vods` | Kick VOD downloads and the VOD editor |

## Machine-readable files

- [OpenAPI](https://kickbot.com/api/v1/openapi.json): every REST endpoint, for code generators and API tools.
- [Agent guide](https://kickbot.com/api/v1/mcp.md): setup, rules, and every tool and field in one Markdown file. You can give it to an AI agent as context.

## FAQ

**Does KickBot have an API?**

Yes. KickBot has a REST API at `https://kickbot.com/api/v1` and an MCP server at `https://kickbot.com/api/v1/mcp`. Both work on every plan.

**Can I use KickBot from ChatGPT or Claude?**

Yes. Add the MCP server URL as a custom connector, then approve the app on the KickBot page that opens. See [Connect an AI app](https://kickbot.com/docs/api/start/connect-ai-apps).

**Can the API post a message in my Kick chat?**

No. No key or app can send a chat message directly. It can set up commands, timed messages and chat alerts, and KickBot posts those the normal way.