AHMEDX
Guide

WASI MD WhatsApp Bot: Features, Session ID and Deployment Guide

WASI MD is a third party WhatsApp Multi Device bot project by Itxxwasi, also presented as Mr Wasi, and the identifiable current project is WASI MD V7 in his own GitHub repository. The original repository is live and was read in full for this guide: its README documents the feature categories and command tables, its .env.example and config.js carry the settings, and its troubleshooting section describes QR authentication with a delete the session folder and rescan flow. The project publishes no pairing website for V7, and the developer separate session generator repository today links to a website that shows unrelated proxy content, so this guide links no WASI MD pairing page as a working service.

By AHMED X · November 12, 2026 · Last verified November 12, 2026

About

What Is WASI MD WhatsApp Bot?

What the project is, who developed it, which version the repository presents, and where its code can be read today.

WASI MD is a third party WhatsApp user bot project by Itxxwasi, also known as Mr Wasi. The identifiable project is WASI MD V7, published in the developer own GitHub repository under the name WASI-MD-V7. That original repository is live today, it is not a fork, and every fact in this guide is checked against it directly. This guide covers only this V7 project and does not merge in features from unrelated WASI MD versions or forks that share the name.

On version, the repository speaks in two places. The README badge and the package.json file both present the project as version 7.0.0, while the botInfo block inside config.js carries a different version string, 7.2.0. This guide reports both values exactly as they stand: 7.0.0 is the version the README and the package file present to readers, and 7.2.0 is the string written inside the configuration file.

The project is built with JavaScript on the Baileys MD library, runs on Node.js, and uses MongoDB for persistent storage. The repository tree holds start.js as the entry point named by the package file, itxxwasi.js as the main application file, config.js for configuration, loader.js and a lib folder holding the database, message handler and plugin loader modules, and the deployment and project files package.json, app.json, heroku.yml, a Procfile, a Dockerfile, docker-compose.yml and .env.example. One honest observation from the tree: the plugins folder ships only two plugin files, menu.js and ping.js, while the wider command library described below is documented in the README tables rather than shipped as separate plugin files in this tree.

The README presents the project in strong terms, calling it the most powerful and feature rich WhatsApp bot built with Baileys MD, and it advertises a command library of more than 250 commands. That number is a claim the project makes about itself in its own README. This guide presents it only as that claim and publishes the specific commands the README tables actually document.

Features

WASI MD WhatsApp Bot Features

The feature categories below are the ones the official README itself documents, in its core features list, its special features list and its command category table. Claims the README makes are recorded as the project own presentation.

Media Downloading

The README downloader category covers YouTube, TikTok, Instagram, Facebook, Twitter and Spotify, with commands for downloading audio and video from those services. The supported commands are listed in the commands section of this guide, exactly as the README table gives them.

Audio Editing

The README audio category lists bass, nightcore, slow, speed and reverse tools for manipulating audio files. The README names the effects and explains nothing further about their output formats.

Image Processing

The README image category lists sticker creation, image conversion, background removal, blurring and enhancement. These are presented in its command category table as image processing and editing tools.

AI Features

The README AI category lists GPT conversation, AI image generation, creative image generation, AI chat and text translation commands. The article record notes that some of these may require external API services or additional configuration, and the README itself does not promise they work without that setup.

Group Management

The README group category covers removing and adding members, promoting and demoting administrators, muting and unmuting the group, anti link protection, and custom welcome and goodbye messages.

Interactive Games

The README games category lists Tic Tac Toe, truth, dare, quiz and slots as entertainment commands shipped with the project.

Automatic Status and Reading

The README special features list automatic status viewing, automatic status reactions with emoji, and automatic message reading. The settings for these live in the environment configuration covered later in this guide.

Anti Delete

The README lists anti delete among its special features, described there as recovering deleted messages. Consider the privacy side before enabling it, because it concerns messages other people chose to remove.

Anti Link and Anti Spam

The README lists anti link group protection and anti spam, which it describes as rate limiting protection. Both appear as toggles in the configuration example the README prints.

Welcome and Goodbye Messages

The README lists custom welcome and goodbye group greetings among its special features, set through the group commands it documents.

Always Online and Auto Typing

The README special features list an always online presence and an auto typing indicator, both controlled from the environment settings.

MongoDB Database

The README lists database integration with MongoDB for persistent storage as a core feature, and MongoDB is a required part of every installation route the project documents. Keep the database connection string private at all times.

Plugin System

The README describes a modular plugin system that makes functionality easy to add or remove, and its development section documents the plugin file format and the plugins directory. As the about section records, the tree itself ships only the menu and ping plugin files.

Web Dashboard

The README core features list includes a web dashboard, described there in one line as a beautiful web interface for management. The README publishes no further detail about what the dashboard contains, so this guide records the feature at exactly that level.

Commands

WASI MD WhatsApp Bot Commands

Unlike many bot projects, the WASI MD V7 README publishes full command tables. The commands below are copied from those tables, with the dot prefix the README and the example configuration both document. The README warns through its own configuration notes that some commands need owner permissions, API access or extra setup.

Basic Commands

The README basic table lists .menu to show all commands, .help for help on a command, .ping to check bot latency, .runtime for bot uptime and .owner to contact the owner. Its tools category also names speed and info.

Downloader Commands

The README downloader table lists .ytmp3 for YouTube audio, .ytmp4 for YouTube video, .tiktok for TikTok video, .instagram for Instagram media, .facebook for Facebook video, .twitter for Twitter media and .spotify for Spotify tracks.

Group Commands

The README group table lists .kick to remove a member, .add to add a member, .promote to make an admin, .demote to remove admin, .mute and .unmute for the group, .antilink to toggle anti link, and .welcome and .goodbye to set the greeting messages.

AI Commands

The README AI table lists .gpt to chat with GPT, .dalle to generate an AI image, .imagine for creative AI art and .translate to translate text. Its category table also names a chat command beside these.

Owner Commands

The README category table names an owner category with broadcast, ban, unban, block and eval. These are owner only by design, and the eval entry in particular is a reminder to review code carefully before running any bot with your number.

Session ID

How to Get a WASI MD Session ID

The V7 README documents QR based authentication and no pairing website for this version. Its troubleshooting section gives the expired session flow directly: delete the session folder, restart and scan a new QR code. The steps below follow the README and state plainly what could not be verified.

01

Start From the Original Repository

Open Itxxwasi/WASI-MD-V7 on GitHub and read the README installation section. It asks for Node.js 18 or above with Node.js 20 recommended, a MongoDB database and Git, and it is the only authentication source this guide trusts for V7.

02

Install and Configure First

Clone the repository, run npm install, copy .env.example to .env and fill in your own settings. The example file describes SESSION_ID as a unique session name you choose yourself, and config.js stores session data in a local session folder, which is why the authentication flow below is built around the running application rather than a website.

03

Start the Application and Watch for the QR Code

Start the bot with npm start. The README troubleshooting section speaks of scanning a new QR code after a restart, which is the authentication the project documents: the running application presents a QR code through its own interface or terminal output. The README does not document a separate pairing code route for V7.

04

Scan With WhatsApp Linked Devices

On Android, open WhatsApp, tap the three dot menu, select Linked Devices, tap Link a Device and scan the code. On iPhone, open WhatsApp, go to Settings, select Linked Devices, tap Link a Device and scan. Wait for WhatsApp to complete the linking before closing anything.

05

If the Session Expires, Follow the README Flow

The README troubleshooting entry for an expired session is short and direct: delete the session folder, restart the bot and scan a new QR code. Only delete the session data of the installation you are refreshing, and expect every connected use of that session to need the fresh link.

06

There Is No Verified WASI MD Pairing Website

The developer also maintains a separate repository called SESSION-GENERATOR, described there as a QR and pair code generator for Baileys based bots in general. Its repository metadata gives session-generator-one.vercel.app as its website, and that address was opened for this guide: today it displays an unrelated proxy session generator for a proxy service, not a WhatsApp pairing interface. This guide therefore does not present it, or any other page, as a working WASI MD pairing website.

07

Protect the Session Like a Password

The example configuration requires SESSION_ID, OWNER_NUMBER and MONGODB_URI, and the README own support material treats these values as private. Anyone holding usable authentication credentials may be able to access the WhatsApp session they came from, so never post your Session ID or your MongoDB connection string in a chat, a screenshot or a public fork.

Deployment

How to Deploy WASI MD WhatsApp Bot

The README carries one click deploy buttons for Heroku, Railway, Render and Koyeb, a VPS procedure with PM2 commands, and Docker instructions with both a build command and a Compose command. The steps below present each route only at the level the README and the repository files support.

01

Fork and Configure Before Any Route

Every route starts from the same base: your own fork or clone of Itxxwasi/WASI-MD-V7, a MongoDB database, and a filled in .env with your own SESSION_ID, OWNER_NUMBER and MONGODB_URI values. The repository carries app.json and heroku.yml for Heroku style deploys, a Procfile, and a Dockerfile with docker-compose.yml for container routes.

02

Heroku: The Deploy Button and app.json

The README one click area carries a Deploy to Heroku button built on this repository, and the tree contains app.json and heroku.yml. app.json names MONGODB_URI, SESSION_ID and OWNER_NUMBER as required settings. The README Heroku section adds one operational step after the build: scale the worker dyno. Check Heroku current availability and pricing before relying on this route.

03

Railway: The Template Button

The README carries a Deploy on Railway button pointing at a Railway template for this repository. Its Railway section is brief: connect the repository, add the environment variables and deploy. The same required values from the configuration section apply.

04

Render: The Deploy Button

The README carries a Deploy to Render button for this repository, and its Render section lists the same shape of steps: create a new web service, connect this repository, add the environment variables and deploy. The tree also carries the Dockerfile a container based Render setup can use.

05

Koyeb: The Fourth Button

The README one click area also carries a Koyeb deploy button for this repository. The README gives the Koyeb route no written procedure beyond that button, so this guide records the button as the documented route and publishes no invented steps for it.

06

VPS: Node.js 20 and PM2

The README VPS section runs on Ubuntu: update the system, install Node.js 20 from the NodeSource setup script, install PM2 globally, clone the repository, run npm install, then start with pm2 start npm --name "wasi-md" -- start, followed by pm2 save and pm2 startup. Its troubleshooting section reads logs with pm2 logs wasi-md and restarts with pm2 restart wasi-md.

07

Docker: Image or Compose

The README installation section documents both container routes directly: docker build -t wasi-md-v7 . followed by docker run with the .env file and port 3000, or docker-compose up -d using the shipped docker-compose.yml. Configure the .env file before either route, because the container reads the same required values.

Configuration

WASI MD Configuration Settings

The settings below are checked against the real .env.example file, the configuration example printed in the README, and config.js. Where those records differ from each other, the difference is stated rather than hidden.

MONGODB_URI

A required setting in .env.example, in app.json and in the README configuration. It carries your MongoDB connection string, credentials included, so it must stay private. The README troubleshooting section ties most database failures back to this value and to the MongoDB Atlas network whitelist.

SESSION_ID

Required in app.json and listed in .env.example, where its own comment describes it as a unique session ID and tells you to choose any name. config.js reads it as the session identifier and stores session data in a local folder beside it.

OWNER_NUMBER and OWNER_NAME

OWNER_NUMBER is required in app.json and appears in .env.example with the instruction to give your WhatsApp number with its country code and no plus sign or spaces. OWNER_NAME sits beside it in the example file. Replace the shipped example values with your own.

PREFIX, BOT_NAME and MODE

The bot settings block of .env.example. PREFIX ships as a dot in both the example file and the README, which is why this guide can state the documented default prefix for this project. MODE chooses between public and private operation, and BOT_NAME sets the display name.

Automatic Behaviour Toggles

.env.example lists AUTO_READ, AUTO_TYPING, AUTO_RECORDING, ALWAYS_ONLINE, AUTO_STATUS_REACT and an automatic status viewing toggle. One honest difference between the records: the example file names that toggle AUTO_STATUS_SEEN, while the configuration example printed in the README names it AUTO_STATUS_VIEW. Check which name your copy reads before relying on it.

Anti Feature Toggles

ANTI_DELETE, ANTI_LINK and ANTI_SPAM appear in the configuration example printed in the README, and config.js reads anti delete and anti link settings, but the three toggles do not appear in the shipped .env.example file. Add them to your own .env only as your copy of the configuration supports, following the files in front of you rather than any copied list.

Official Links

WASI MD Official Links

The resources checked for this guide: the original repository and the exact files verified inside it, the developer profile, the separate session generator repository with its present day status stated, and the library the bot is built on.

WASI MD V7 GitHub Repository

The original Itxxwasi/WASI-MD-V7 repository, live today and not a fork. It carries the README, .env.example, config.js, package.json, app.json and the repository tree this guide verified against.

https://github.com/Itxxwasi/WASI-MD-V7

WASI MD V7 README

The README inside the original repository: the feature lists, the command tables, the configuration example, the deploy buttons and the troubleshooting section this guide is built from.

https://github.com/Itxxwasi/WASI-MD-V7/blob/main/README.md

WASI MD app.json

The Heroku style configuration file in the repository, which names MONGODB_URI, SESSION_ID and OWNER_NUMBER as the required settings at deploy time.

https://github.com/Itxxwasi/WASI-MD-V7/blob/main/app.json

WASI MD .env.example

The shipped example environment file. It is the record this guide used for the real setting names, including the AUTO_STATUS_SEEN spelling that differs from the README example.

https://github.com/Itxxwasi/WASI-MD-V7/blob/main/.env.example

Developer GitHub Profile

The Itxxwasi account that publishes WASI MD V7 and the separate session generator repository.

https://github.com/Itxxwasi

Developer Session Generator Repository (Website Not a Pairing Page)

The Itxxwasi/SESSION-GENERATOR repository, a separate general purpose generator for Baileys based bots. The website its repository metadata advertises was opened for this guide and today displays an unrelated proxy session generator, not a WhatsApp pairing interface, so it is not linked here as a pairing service.

https://github.com/Itxxwasi/SESSION-GENERATOR

Baileys Library

The current home of the Baileys library under the WhiskeySockets name. The WASI MD README credits Baileys as the WhatsApp library the bot is built with.

https://github.com/WhiskeySockets/Baileys

Safety

Is WASI MD WhatsApp Bot Safe?

The precautions that apply to WASI MD, including the warning its own README prints, the state of its session routes, and the disagreement inside its license record.

WASI MD is an unofficial third party bot, and its README prints the warning itself: the bot is for educational purposes only, the developer is not responsible for misuse, and users should follow WhatsApp Terms of Service. Take that warning at face value. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and no feature in any bot can promise protection from that. Use a separate number for testing rather than your main personal or business number, and avoid spam and abusive automation of any kind.

Be careful where you authenticate. The V7 project documents QR authentication through its own running application and publishes no pairing website. The one website attached to the developer separate session generator repository today shows unrelated proxy content instead of a WhatsApp pairing interface. Only trust authentication routes you can trace back to the project documentation itself, and treat every other WASI MD session page as unverified. Protect the values that guard the account: your Session ID, your MongoDB connection string and your database password should never appear in a public repository, a screenshot or a group chat.

On licensing, the records inside the original repository point one way but leave a gap. The README carries an MIT badge, its license section states the project is licensed under the MIT License, and the license field of package.json also reads MIT. However, that README section points readers to a LICENSE file for the details, and no LICENSE file exists in the repository tree today; the GitHub API likewise detects no license for the repository. This guide reports all of those signals exactly as they stand, so readers should know the MIT naming rests on the README and the package file rather than on a license text file that can be opened in the tree.

Alternatives

Free MD Bots You Can Deploy on AHMED X

Want more free MD bots like this? These bots on AHMED X cover the same ground: free deploy, pair-code setup, group and chat automation.

ASTRA X

ASTRA X

WhatsApp MD Bot

Advanced AI-first MD bot with dual AI engines, media downloaders and deep group management.

Geston-MD

Geston-MD

WhatsApp MD Bot

Lightning-fast Baileys multi-device bot with AI chat, group protection and replies in many languages.

CELESTIA

CELESTIA

WhatsApp MD Bot

A polished multi-device WhatsApp bot with a large command library, AI chat and safe group tools.

TOXIC-MD

TOXIC-MD

WhatsApp MD Bot

Lightning-fast WhatsApp bot built on Baileys, made for speed and everyday automation.

SUKUNA-MD

SUKUNA-MD

WhatsApp MD Bot

A modular WhatsApp MD bot with group administration, media tools, protection engines and AI voice replies.

Levanter

Levanter

WhatsApp MD Bot

Multi-device WhatsApp bot packed with group protection, AI chat and a plugin system.

View all bots in the catalog

FAQ

WASI MD FAQs

Short answers to the questions readers ask most about WASI MD.

WASI MD is a third party WhatsApp Multi Device bot project by Itxxwasi, also known as Mr Wasi. The current identifiable project is WASI MD V7 in his own GitHub repository, built on Baileys with Node.js and MongoDB. Its README documents media downloading, audio editing, image processing, AI tools, group management, games and automation features.

Itxxwasi, also known as Mr Wasi. The README names MR WASI as the developer, the package file gives its author as ITXXWASI, and the project is published from the Itxxwasi GitHub account.

The README badge and package.json both present version 7.0.0, while the botInfo block inside config.js carries the version string 7.2.0. This guide reports both exactly as they stand rather than choosing between them.

Through the running application, not a website. Install the project, copy .env.example to .env, fill in your settings, start the bot and scan the QR code it presents with WhatsApp Linked Devices. If the session later expires, the README troubleshooting flow is to delete the session folder, restart the bot and scan a fresh QR code.

No verified one could be confirmed. The V7 README documents QR authentication only. The developer separate SESSION-GENERATOR repository advertises a website that today displays an unrelated proxy session generator rather than a WhatsApp pairing interface, so this guide links no pairing website for WASI MD.

Its one click area carries deploy buttons for Heroku, Railway, Render and Koyeb, and the README also documents a VPS route with Node.js 20 and PM2 commands and Docker routes using the shipped Dockerfile and docker-compose.yml.

The README badge, the README license section and the package.json license field all name the MIT License. However, the LICENSE file the README section points to is not present in the repository tree, and the GitHub API detects no license for the repository, so the MIT naming rests on those three records rather than on an openable license file.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the WASI MD records that could be opened on the last verified date: the original Itxxwasi/WASI-MD-V7 repository, read through the GitHub API and its raw files, including its README with the deploy buttons and command tables, its .env.example, config.js, package.json, app.json and its full repository tree, together with the developer SESSION-GENERATOR repository and the website that repository advertises, which was opened and found to display unrelated proxy session content. On that date the original repository was live, the version records disagreed between 7.0.0 and 7.2.0 as this guide records, and no LICENSE file was present in the tree. Where the records publish nothing, this guide says so instead of filling the gap.

AHMED X provides this article for educational and informational purposes only. AHMED X is not the developer or owner of WASI MD and does not claim any partnership or official affiliation with Itxxwasi or the project contributors.

AHMED X is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta. WhatsApp is a trademark of its respective owner. Use unofficial WhatsApp automation at your own risk.

Keep Reading

Related WhatsApp Bot Guides

More free WhatsApp bot guides from the AHMED X blog.

Guide

XBOT MD WhatsApp Bot: Features, Session ID and Deployment Guide

XBOT MD, written X BOT MD inside its repository, is a third party WhatsApp Multi Device bot project by Aswin Sparky. The original repository is live today under the renamed Aswin-Sparky account, with the older A-S-W-I-N-S-P-A-R-K-Y address redirecting to it, and this guide is checked against that repository directly: its README documents QR authentication and four deployment routes, and its session service was opened again for this guide and is working, asking visitors to sign in with GitHub and fork the repository before it offers QR pairing and a pair code option. A separate pairing project by the same developer exists only as source code to host yourself, and the README publishes no command list, so this guide publishes none.

Read the guide
Guide

ZOKOU MD WhatsApp Bot: Features, Session ID and Deployment Guide

ZOKOU MD, also known as Zokou 2.0, is a third party WhatsApp Multi Device bot project by Djalega++ and Monkey D Luffy, documented in a French language README in its original GitHub repository. That repository is live today and was read in the original French for this guide: it documents the feature list, links one session website, and gives Heroku and Koyeb deployment routes. The session website was opened again for this guide and its QR route loads, while the pairing code destination it links out to returns a 404 error, and the README Heroku button in fact templates a different repository, so this guide states the present day condition of every route plainly.

Read the guide
Guide

MD Bot WhatsApp: Complete Beginner Guide to Features, Session ID and Deployment

An MD bot WhatsApp application is an automated WhatsApp bot that connects to an account using WhatsApp Multi Device functionality. These bots can help users automate messages, manage groups, download media, create stickers, and perform other tasks through WhatsApp commands. Many WhatsApp MD bots are available as open source JavaScript projects. Beginners can choose a project, connect their WhatsApp account using a QR code or pairing code, and run the bot on a computer, VPS, or supported cloud hosting service.

Read the guide
Guide

WhatsApp MD Bot: Types, Features and How to Choose the Best One

A WhatsApp MD bot is an automated application that connects to a WhatsApp account through Multi Device functionality. These bots are available in different categories, and each category is designed for a different purpose. Some WhatsApp MD bots focus on group management, while others provide media downloading, AI assistance, entertainment commands, or simple automatic replies.

Read the guide

Deploy Your Own Free WhatsApp Bot Today

Pick a bot from the AHMED X catalog and deploy it free in minutes. No server, no coding.

Browse Free Bots