Questions and answers

A bot you invite to your Discord server and tell, in plain words, what should happen there: channels, roles, permissions, messages. If you prefer, you use your own bot in Claude or ChatGPT instead; the tools are the same.

No. With our bot, setting up is one click on Invite, and using it is one sentence in a channel. With your own bot there is a token to paste as well. Nothing here asks you to write anything technical.

Ours, or yours. Invite our bot D.MCP and you need no application of your own: one click, and it makes a channel where you write to it. Bring your own and you create the Discord application in your own developer account, the token belongs to you, and you can revoke it at any moment without asking us.

Not with our bot. You write to it in a channel on your server, and the model that understands your sentences runs with us and is included in the price. You need Claude or ChatGPT only if you want to use your own bot there.

Yes. The address is a standard MCP connector, and both accept one. Anything else that speaks MCP works too. And with our bot you need neither: you write to it in Discord, and the model is included.

42 tools from the start, 9 more you can switch on. Make, edit and copy channels and roles, hand roles out and take them back, post, edit, pin and react to messages, run polls, open threads, make invites, put events in the sidebar, and read any of it back, down to the audit log. Copying a channel brings every permission on it across.

Nothing that cannot be undone. Deleting channels, deleting other people’s messages, deleting roles, wiping reactions, kicking, timing out, banning, revoking invite links and cancelling events: all of it is off until you switch it on behind a warning. The same goes for rights it may give roles or members: everything that reaches past a channel, such as moderation, bans, other people’s messages, roles, the server and webhooks, is off until you switch it on. Administrator it can never grant.

Yes, with our bot. If you ask it for something that is off, it shows a card with exactly the text the portal shows, and a button. Only the account holder may press it, and the model itself cannot press that button. Switching off works there the same way, and in the portal at any time.

Because one can be undone and the other cannot. Archiving moves the channel out of sight and keeps every word in it. Deleting takes the messages with it and Discord has no way to bring them back.

Into a category called Archive on your server, made the first time it is needed. From then on it is out of sight for everybody else and writing in it is switched off. You, running the server, still see it. Nothing is deleted: every word stays readable. Bringing it back costs a sentence to your assistant, or two clicks in Discord.

Yes, on anything that cannot be undone: five such actions in any ten minutes, counted across all of them together, and thirty in ten minutes for deleting single messages, counted on their own. Tidying up after a project is three or four. A server being taken apart is not. Whoever wants a channel emptied is offered to archive it and set the same channel up afresh instead: nothing is lost, and nothing is counted.

No, and that is deliberate. A limit you can raise from a screen gets raised the first time it says no, which is the exact moment it is doing its job.

With our bot there is no token of yours. If you bring your own bot, its token is erased the moment your instance confirms it started. On the way there it passes through here, and what stays afterwards is a fingerprint: enough to notice the token changed, not enough to use it.

No. Every customer gets their own process, their own address and their own certificate, and there is no shared database. With your own bot there is no shared bot either. With ours there is one, and its token lives in a single process that ties every request from an instance to that instance’s own server and refuses everything else.

You, as the account holder, and whoever you add: a list of Discord users on your server’s page in the portal. Whoever only reads along in the channel cannot command anything, and the bot knows for every instruction who gave it.

Only the channel it made. It does not read other channels, even where it could see them. What you write to it there goes to the model once, to be carried out, stays in memory for a few hours so that the next sentence can refer to it, and is not written to disk.

The ones the tools use, and Administrator. No tool needs that one, but without it the bot cannot enter a channel it is not named in, and on a server that already exists those are often the important ones. With our bot it is the same set, granted once to it rather than to yours.

Anybody who can write on your server can try, and that is the risk the whole product is built around. The assistant reads text other people wrote and cannot reliably tell an instruction from a description of one. So the dangerous tools do not exist at all unless you switch them on, and the ones that do are rationed.

Yes. Every change is written to a log channel on your own server, and every refusal too, with our bot as with yours. The refusal is the more interesting half: an attempt that never reached Discord leaves no trace anywhere else.

A channel on your server, made during setup: by you with your own bot, by our bot beside its own channel. Every change and every refusal is written into it. It is hidden from @everyone, because a list of every change made to your server does not belong published inside that same server. Whoever should see it gets access from you, in Discord.

Renaming and moving it, yes, that changes nothing. Deleting it, better not. Your tools carry on working and no change is lost, only its record, and your instance reports an error on every attempt from then on. Above all you lose the more interesting half: a refused attempt is visible nowhere else. If it does go, write to us and you will get a new one.

The channel our bot makes on your server as soon as you have invited it. At first only you can see it. There you write what should happen, and there it answers. Who else you let in is your call, in Discord; reading along is not commanding.

With our bot about a minute: sign in, invite, write in the new channel. With a bot of your own about 5 minutes, and nothing has to be prepared in advance. We walk you through creating the Discord application, pasting the token and picking the server.

No. The invite link asks for everything the tools need. What is left to do by hand happens here in the portal rather than in Discord: switching on the tools that are off, if you want one of them.

Yes, up to 2 Discord servers on one plan. Each server is its own instance with its own address and its own switches, and with its own bot if you bring one. Our bot can be on several of your servers; each gets its own channel. They share nothing.

With our bot you have both: the channel, and the address of your instance to enter into Claude or ChatGPT; it is on your account page. From your own bot to ours you switch by shutting the instance down and inviting our bot. That takes a minute, and your server stays as it is.

Then Requires OAuth2 Code Grant is switched on for your application. It is off by default and it belongs off: switched on, Discord refuses every invite with that sentence. Switch it off in the Developer Portal, under your application on the Bot tab, and paste the token again. That does not change the token.

Look at Your MCP in your account first: the top of that page says whether your instance is running, when it was last used, and how old that reading is. With our bot it also says which channel it answers in. If that is not it, ask in the support channel. The bot answers first, and a person is always reachable behind a visible second button.

Your instance keeps running for 3 more days from that moment, then stops. Nothing is deleted while it is stopped, and starting it again picks up where it left off.

Nothing extra. It is part of the plan, with a ceiling per server and month so that a mistake cannot get expensive. That ceiling is deliberately not a setting.

The instance is stopped and its directory is set aside. Your Discord server is untouched: every channel, role and message stays exactly as it was, because all of it always lived on Discord rather than here.