Skip to content
Kotbo
FR, version française

Kotbo 4 min read

Manage your Discord server with AI: plug Claude, ChatGPT or Gemini into Kotbo

For an AI to manage your Discord server, it needs access to your data and the right to act, which is what an MCP server provides. Kotbo has one: you create a key in the dashboard, paste a URL into your AI, and it reads your tickets, sanctions or staff, then acts within the limits you ticked

Add to Discord Dig through the dashboard demo

Included in every plan, with a 15-day trial and no credit card

What a Discord MCP server is

MCP, the Model Context Protocol, is an open standard that hands tools to an AI: read a list, send a message, change a setting. Kotbo’s MCP server, still in beta, exposes your Discord server as tools that Claude, ChatGPT or Gemini call when your request needs them. An AI Discord bot chats with members in a channel. Here, the AI stays your assistant, outside Discord, and you’re the one talking to it

Connecting Kotbo to Claude, ChatGPT or Gemini

Setup happens on the dashboard’s Connect an AI page, which only people who manage the server’s settings can open. The Connection Help button walks through each AI

  1. Create a key

    New key, a name that says where it’s used (Claude.ai for instance), then the permissions. The secret is shown once: copy it right away

  2. In Claude

    Customize, then Connectors, the + button and Add custom connector. Paste Kotbo’s MCP URL, or the Claude direct URL if authorisation gets stuck

  3. In ChatGPT

    Settings, Apps, Advanced settings, turn on Developer mode, then Create app with a remote MCP server, Kotbo’s URL and OAuth authentication

  4. In Gemini

    On the API side, add a tool of type mcp_server with Kotbo’s URL, plus an Authorization: Bearer header with your key if your client doesn’t handle OAuth

  5. Allow access

    On the first call, your AI opens a Kotbo page asking for your key. Click Allow access, and the AI can see your server

What you can ask the AI to do

Each request goes through specific tools, which the AI picks on its own. A few examples, with the real tool names

  • Handle tickets

    get_tickets lists the pending ones, reply_ticket answers in the ticket as the bot, close_ticket closes it

  • Pull a sanctions report

    get_sanctions and get_sanction_history for the record, apply_sanction to sanction the accounts behind a raid

  • Keep track of staff

    get_staff_list, get_staff_absences and get_staff_tasks to see who’s around and who’s lagging, generate_staff_evaluation for a review

  • Read server health

    get_pulse_dashboard returns the Pulse score, get_hourly_activity the hours when people talk

  • Configure the server

    set_module_activation turns a module on, create_channel and create_role build the structure, create_announcement posts an announcement

  • Write the server’s website

    create_site_page and publish_site_page write and publish a page. While the AI writes, human editing goes read-only, and you can interrupt it from the dashboard

Permissions for each key

A key only does what you ticked when you created it. Without the permission, the tool refuses

  • Read: stats, members and messages, sanctions, staff, tickets, community, economy, moderation, analytics, automations, site
  • Write: sanction, manage messages, tickets, community, members, automations and the site
  • Automations deserve a trusted key: once active, an automation acts on its own, sanctions included
  • A key acts on behalf of the account that created it: if that account loses access to the server’s dashboard, the key stops working
  • Revoking a key cuts the AI off immediately

The log: who did what

An AI acting without a trace would be a ghost moderator. Every action that goes through the MCP server is logged on the dashboard’s Staff actions page, under the name MCP[key name]. A sanction issued by the AI carries that same name as moderator in the member’s record. The Connections button on the Connect an AI page also shows recent connection attempts, useful when an AI can’t connect

AI Discord bot or MCP server

They answer different needs, and searches for an AI Discord bot often mix the two up

  • An AI bot in the server

    It chats with members in a channel, to liven things up or answer common questions

  • An MCP server

    It gives your AI the tools of your dashboard. Handy for staff: ask a question in plain English, and the AI reads, cross-checks and acts for you, within its key’s rights

Frequently asked questions

How do I manage a Discord server with AI?

Connect your AI to an MCP server that knows your server. With Kotbo: create a key on Connect an AI, paste the URL into Claude, ChatGPT or Gemini, and allow access

Which AI works with Kotbo’s MCP server?

Claude through a custom connector, ChatGPT through a developer-mode app, Gemini through an mcp_server tool on the API. Any MCP client that sends a Bearer token works too

Can the AI ban someone without me?

Only if its key has the Sanction permission. Without it, apply_sanction refuses, and every sanction issued by the AI is signed MCP followed by the key name

What does the AI see of my server?

Whatever the read tools its key allows return, when it calls them. Those results go to your AI provider, like the rest of your conversation

How do I cut an AI’s access to my Discord server?

Revoke its key on the Connect an AI page. Access stops right away, including the direct URL generated for Claude

What is a Discord MCP server?

A service that exposes a Discord server’s actions to an AI, as tools it calls with your permission. Kotbo’s covers tickets, sanctions, staff, settings and the website

Try it on your server

15 days free, no credit card. Every plan includes the whole catalog

Add to Discord See pricing