> For the complete documentation index, see [llms.txt](https://docs.kickbot.com/dashboard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kickbot.com/dashboard/api/readme.md).

# KickBot API and MCP

The KickBot 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.

You can connect an AI app (ChatGPT, Claude, Grok, Cursor, and others) or your own code to your KickBot channel. It can then set up and run the same things you manage in the dashboard: custom commands, timed messages, TTS, chat alerts, overlays, widgets, tipping, clips, VODs, and more.

{% hint style="info" %}
This guide assumes you have a KickBot account with your Kick channel connected. The API is free on every plan. The limits of your plan (for example, the number of enabled custom commands on the free plan) are the same in the API as in the dashboard.
{% endhint %}

## 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.

## 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 (for example, enabled custom commands on the free plan) and field limits (for example, 500 characters for a command reply).
* It cannot see or change billing, payouts, refunds, 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 **API & MCP > Recent API activity** in the dashboard.

## Next steps

* [Connect an AI app](/dashboard/api/connect-ai-apps.md)
* [Create and use API keys](/dashboard/api/api-keys.md)
* [Quickstart with the REST API](/dashboard/api/quickstart.md)
* [Build your own agent](/dashboard/api/build-an-agent.md)
* [Errors and limits](/dashboard/api/errors-and-limits.md)
* [Permissions and security](/dashboard/api/permissions-and-security.md)
* Machine-readable: [OpenAPI](https://kickbot.com/api/v1/openapi.json) and the [agent guide](https://kickbot.com/api/v1/mcp.md)

## Need help?

Email <support@kickbot.com> or ask in the `#support` channel on [Discord](https://discord.gg/MAg3gBbc89).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kickbot.com/dashboard/api/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.