ServerDB sets itself up when it joins to a server. ServerDB lets server administrators insert keys and values just like a dictionary and lets server administrators modify existing key values or delete them entirely. ServerDB acts as your Discord server's own database and how you use this database is entirely up to you.

Our bot has an user-friendly interface, every command is well explained and you'll be informed about what you are doing.

Examples of data to store

  • Storing role IDs
  • Storing user IDs
  • Storing string values


Bots can access to any server's database as long as they are in the server. Authentication process is easy and you don't need an API key in order to retrieve any data. ServerDB API works with get requests with 3 simple parameters.


Your bot no longer has to spam users with configuration messages and store their data in your own databases. Instead, your application can connect to ServerDB API and retrieve the desired data for your application to work. If servers update one of the records in our databases, they no longer have to update/re-configure every single bot in their servers.


You will no longer need to configure each bot and remove all the hassle, update everything in ServerDB, we'll do the rest for you!


Think of a moderation bot that appends the muted role to a user when mute command is executed. This bot will need to know which role in the server is muted role, therefore it requires the server administrators to provide "muted" role id for this bot to work properly. Bots can find roles with names, but what if the muted role in your server is in a different language? Maybe it starts with a symbol? That's what the bot can't detect on its own. ServerDB's role here is simple, server administrators insert muted role id to our service, and we provide it to the bot directly. If it gets updated, every bot will use the new value in real time.