AHMEDX
Guide

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

PRINCE MD is a third party WhatsApp Multi Device bot project by Prince Mayel, written in JavaScript with the Baileys library. Its README promises a bot with lots of features and packages but publishes no feature list and no command list, so this guide builds its picture only from what the repository itself proves: the toggles and defaults inside config.js, the three setup steps in the README, and the deployment files the repo ships. It also states the awkward findings plainly: the session page the README links returns a 404 error today, the developer website is offline, the application file the bot actually runs ships obfuscated, and the repository contains session files that were committed to it.

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

About

What Is Prince MD WhatsApp Bot?

What the project is, who develops it, what it runs on, and how little its README actually documents.

PRINCE MD is a third party WhatsApp Multi Device bot project developed by Prince Mayel, who also publishes under the name PRINCE TECH. It is written in JavaScript and connects through the Baileys library. The package.json file names the package PRINCE-MD-V2 at version 2.6.0, gives server.js as the main file, and sets the start script to run it with Node.js. When the bot starts, server.js launches index.js.

The README describes the project in one enthusiastic line, calling it an awesome WhatsApp bot with lots of features and packages to make your WhatsApp interesting. It then stops: the README publishes no feature list, no command list and no deployment tutorial. Its whole setup section is three steps: fork the repository, get a Session ID or creds.json file, and upload that file into the PRINCESESSION folder. Everything in this guide beyond those steps comes from the project files themselves, chiefly config.js.

The repository holds the main application file PRINCE-MD-V2.js, the configuration file config.js, and folders named lib, prince, src, database, storage, Assets and HostMedia. Files named for MAKINO-MD-V2 survive inside the Assets and HostMedia folders, and the repository field inside app.json still points at that earlier project, which shows this code base was built on top of it.

Two honest limits run through this guide. Because the project documents no commands, this guide prints no command list and invents none. And the login services around the project are in poor shape: the session page the README links and the developer website the repository points to were both checked for this guide and both returned a 404 error, which the session section below explains in full.

Features

Prince MD WhatsApp Bot Features

The README documents no feature list, so every item below is a setting that actually exists in the published config.js, with the default it ships with stated openly. Anything config.js does not contain is not listed.

Session Authentication

The bot connects with a Session ID that config.js reads from the environment, or with a creds.json credentials file placed in the session folder the README names. Authentication is the one setup step the README spends most of its words on.

Automatic Status Viewing

The autoviewstatus setting ships switched on, making it the only automatic behaviour enabled by default. With it on, the bot views WhatsApp statuses by itself.

Automatic Message Reading

Two settings, autoReadGc for group chats and autoReadAll for all chats, ship switched off. Turning one on makes the bot mark incoming messages as read automatically.

Automatic Typing and Recording Presence

The autoTyping and autoRecord settings ship switched off. They control whether the bot shows a typing or a recording presence inside chats.

Call Control

The anticall setting ships switched off. It is the configuration point for how the bot treats incoming calls on the connected number.

Anti Tag Control

The antitags setting ships switched off. It is a control aimed at messages that tag the bot or its owner, a common annoyance in busy group chats.

Custom Bot Identity

config.js carries the bot name, the owner name, a sticker pack name and sticker author, a menutype setting for the menu style, and logo and thumbnail images loaded from the Assets folder, so the visible identity of the bot can be personalised.

Permission Messages

The configuration ships ready written replies for owner only commands, group admin commands, group only commands and private chat only commands. That proves the command system separates owner, admin and ordinary member access, even though the project publishes no list of the commands themselves.

Session ID

How to Get a Prince MD Session ID

The README setup is three steps: fork the repo, get a Session ID or creds.json, then upload the creds.json into the PRINCESESSION folder. The session page its second step links was opened and checked for this guide and no longer loads, so this section records exactly what the README says and exactly what the check found.

01

Fork the Repository

The first README step is to fork github.com/Mayelprince/PRINCE-MD into your own GitHub account, so the copy you configure and deploy is yours.

02

The Session Page the README Links

The second README step, Get Session ID or CREDS.JSON, carries a badge that links to a session page hosted on Render at prince-md-v2-session-id-w9re.onrender.com. That page was opened for this guide and returned a 404 error, which means the service behind it is gone. No working official session service for PRINCE MD could be confirmed today, and this guide links none as a live service.

03

Use Only Your Own Credentials

Whatever route you use to link an account, the credentials must be your own. Never reuse the default Session ID value that ships inside config.js: the file contains one as a fallback, it sits in a public repository where anyone can read it, and a value everyone can read is not private to you. Set your own value in the SESSION_ID environment setting instead, and treat unknown session generator sites with suspicion.

04

Upload creds.json Into PRINCESESSION

The third README step says to upload the creds.json file you obtained into the PRINCESESSION folder. One wrinkle: no folder with that exact name exists at the top level of the repository as shipped, so you may need to create it. The repo does ship a lib/princesession folder, and it already contains session files, including a creds.json, that were committed to the public repository. Delete or replace anything that ships with the code, and never reuse credentials that came with a public repo.

05

Keep the Session Private

A Session ID or creds.json file gives access to the WhatsApp account it came from. Keep yours out of public repositories, chats and screenshots, and if you stop using the bot, open WhatsApp, go to Linked Devices, and remove its connection.

Deployment

How to Deploy Prince MD WhatsApp Bot

The README names no hosting provider and gives no deployment tutorial, so this section separates what the README documents from what can only be read out of the files the repository ships: an app.json and a Procfile in Heroku style, a replit.nix file, and the package.json scripts. Hosting panels, limits and prices change, so check your chosen provider for its current terms.

01

What the README Actually Documents

The complete documented setup is the three README steps: fork the repository, get a Session ID or creds.json file, and upload the creds.json into the PRINCESESSION folder. Any hosting route beyond that is assembled from the project files, not from instructions the developer published.

02

Heroku Style Files

The repository ships an app.json file that asks for a SESSION_ID value, marks it required, and lists the Node.js buildpack together with ffmpeg and webp buildpacks, plus a Procfile that runs a worker process with node server.js. Those are the files a Heroku style deployment uses, but the README never confirms a working Heroku procedure, so treat the route as plausible rather than promised.

03

Replit File

A replit.nix file ships in the repository, which means a Replit environment definition is included in the project. The README provides no Replit tutorial and confirms nothing about running the bot there.

04

Run It Yourself

The package.json start script is node server.js, and that is verifiable from the file itself. Clone the repository, run npm install, place your own creds.json or set your own SESSION_ID, review config.js, then run npm start on a machine that stays online. server.js launches index.js, and the bot connects with the credentials you provided.

05

After It Starts

Watch the terminal or hosting logs for the WhatsApp connection. If commands do not respond, check that the prefix in config.js matches what you are typing and whether the command is restricted to the owner or to group admins, because the configuration reserves some commands for those roles.

Configuration

Prince MD Configuration Settings

The settings below are the ones config.js actually defines, with the defaults the file ships with. Follow the exact names the file uses.

SESSION_ID

The session value the bot connects with, read from the environment before anything else. A fallback value ships inside config.js; replace it with your own and never share it.

Owner and OwnerName

The owner number list and the owner name the bot answers to. Owner level commands are reserved for the number set here.

BotName

The name the bot presents, which ships as PRINCE-MD-V2. The sticker pack name and sticker author settings sit beside it in the same file.

prefa

The command prefix list. As shipped it holds a single dot, so commands begin with a dot unless you change the setting.

autoviewstatus

Automatic status viewing, and the one automatic behaviour that ships switched on. Set it to false in config.js if you do not want the bot viewing statuses by itself.

autoReadGc and autoReadAll

Automatic message reading for group chats and for all chats. Both ship switched off.

autoTyping and autoRecord

Automatic typing and recording presence inside chats. Both ship switched off.

anticall and antitags

The call control and anti tag settings. Both ship switched off.

menutype

The menu style setting, which ships as v3. It sits with the packname and author settings that shape how the bot and its stickers present themselves.

Official Links

Prince MD Official Links

The resources checked for this guide: the repository and its key files, the project WhatsApp channel the README links, and the documented services with their check results stated honestly.

PRINCE MD GitHub Repository

The project home by Mayelprince, with the README, config.js, package.json and every other file this guide verified against.

https://github.com/Mayelprince/PRINCE-MD

PRINCE MD README

The short README with the three setup steps, the session badge and the ban warning in the developer own words.

https://github.com/Mayelprince/PRINCE-MD/blob/main/README.md

PRINCE MD config.js

The configuration file this guide drew its features and defaults from. It contains a fallback Session ID value; never reuse it.

https://github.com/Mayelprince/PRINCE-MD/blob/main/config.js

PRINCE MD package.json

The package file naming the package PRINCE-MD-V2, declaring server.js as the main file and the start script, and listing the Baileys dependency.

https://github.com/Mayelprince/PRINCE-MD/blob/main/package.json

PRINCE MD WhatsApp Channel

The WhatsApp channel the README and the configuration both link for project updates.

https://whatsapp.com/channel/0029VajcRr0GpLHR6PjdgN3N

Documented Session Page (Offline)

The session ID page on Render that the README badge links. It returned a 404 error when checked for this guide and is listed for the record, not as a working service.

https://prince-md-v2-session-id-w9re.onrender.com

Developer Website (Offline)

The website address the repository homepage field points to. It returned a 404 error when checked for this guide and does not load today.

https://prince-md.vercel.app/

Safety

Is Prince MD WhatsApp Bot Safe?

The precautions that apply to PRINCE MD, including the warnings its own README and its own files raise.

The README carries the warning itself: the bot is not made by WhatsApp Inc, misusing the bot might ban your WhatsApp account, the developer is not responsible for banning your account, and you use it at your own risk. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and no setting in any bot can promise protection from that. Use a separate number for testing rather than your main personal or business number.

Review what you are actually running. index.js, the file server.js launches when the bot starts, ships obfuscated, so its code cannot be read plainly to check what it does. The repository also ships session files committed inside lib/princesession, including a creds.json, and a fallback Session ID value inside config.js. Replace every credential that ships with the code with your own, delete session files you did not create, and never hand your own Session ID or creds.json to anyone.

A session value is account access. Keep it in a private environment setting, out of public repositories and screenshots, and remove the bot from WhatsApp Linked Devices when you stop using it. Never use the bot for spam or abusive automation.

On licensing, the repository carries a LICENSE.md file with the full MIT License text, copyright held by PRINCE TECH, GitHub detects the license as MIT, and package.json states MIT as well. Treat PRINCE MD as an MIT licensed project: you may use, copy and modify it under the MIT terms, keeping the license notice with the code.

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.

View Bot PageDeploy Free
Geston-MD

Geston-MD

WhatsApp MD Bot

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

View Bot PageDeploy Free
CELESTIA

CELESTIA

WhatsApp MD Bot

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

View Bot PageDeploy Free
TOXIC-MD

TOXIC-MD

WhatsApp MD Bot

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

View Bot PageDeploy Free
SUKUNA-MD

SUKUNA-MD

WhatsApp MD Bot

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

View Bot PageDeploy Free
Levanter

Levanter

WhatsApp MD Bot

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

View Bot PageDeploy Free
View all bots in the catalog

FAQ

Prince MD FAQs

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

PRINCE MD is a third party WhatsApp Multi Device bot project by Prince Mayel, who also publishes as PRINCE TECH. It is written in JavaScript with the Baileys library, and its package.json names the package PRINCE-MD-V2. Its README promises lots of features and packages but publishes no feature list and no command list.

The README setup says to get a Session ID or creds.json file, and its badge links to a session page hosted on Render. That page returned a 404 error when checked for this guide, so no working official session service could be confirmed. Use only credentials generated for your own account, and never reuse the fallback Session ID value that ships inside config.js.

The README says to upload the creds.json file into the PRINCESESSION folder. No folder with that exact name exists at the top level of the repository as shipped, so you may need to create it. The repo also ships a lib/princesession folder containing session files committed to the public repository; replace anything there with your own credentials.

A dot. The prefa setting in config.js holds a single dot as shipped. The project publishes no command list, so this guide lists no commands; the configuration does show that some commands are reserved for the owner and some for group admins.

The README lists none. What config.js documents is a set of toggles: automatic status viewing switched on by default, and automatic message reading for groups and for all chats, automatic typing and recording presence, call control and anti tag control, all switched off by default, alongside bot name, owner name, sticker pack and menu style settings.

The README names no hosting provider and gives no deployment tutorial. The repository ships an app.json and a Procfile in Heroku style and a replit.nix file, and its package.json start script runs the bot with node server.js, so running it yourself on a machine that stays online is the route the files directly support.

MIT. The repository carries a LICENSE.md file with the full MIT License text, GitHub detects the license as MIT, and package.json states MIT too. You may use and modify the code under the MIT terms, keeping the license notice.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the PRINCE MD repository itself at github.com/Mayelprince/PRINCE-MD, chiefly its README, config.js, package.json, app.json, Procfile and LICENSE.md, all checked on the last verified date. On that date the session page the README links and the developer website the repository points to each returned a 404 error, and the repository itself was last updated in March 2025. Where the project publishes 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 PRINCE MD and does not claim any partnership or official affiliation with Prince Mayel, PRINCE TECH 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

Queen Elisa MD WhatsApp Bot: Features, Session ID, QR Setup and Deployment Guide

QUEEN ELISA MD is a third party WhatsApp user bot project created by Mr Nima, who publishes under the name darkmakerofc, built with Node.js and the Baileys library. Researching it honestly means facing a records problem first: both GitHub repositories the project points to are blocked by GitHub and return a 404 error today, so this guide is built only from the records that can still be read, a full copy of the project preserved on GitLab, the npm package queen-elisa-md at version 4.0.4, and a community copy from 2022. Those records carry different versions and different setup instructions, and this guide keeps them separate instead of merging them into one story.

Read the guide
Guide

Queen Jennifer MD WhatsApp Bot: QR Code, Configuration and Deployment Guide

QUEEN JENNIFER MD is a third party WhatsApp user bot project maintained by zeqanpx on GitHub, built on the Baileys Multi Device library. Its documentation is unusually thin: neither the repository README nor the project documentation site publishes a feature list or a command list, so this guide covers only what the project files themselves verify. The project also carries a harder problem, stated at the top of its own README: it is not working, because the original Baileys package it depends on was removed. This guide records the project as it stands today, with its dead QR scanner page and its unsupported Heroku button stated plainly.

Read the guide
Guide

Queen MD WhatsApp Bot: QR Code, Session File and Deployment Guide

QUEEN MD is a third party WhatsApp Multi Device bot project by DarkWinzo on GitHub, built on the Baileys library. Its repository description presents it as the first Sinhala Multi Device WhatsApp bot. The first fact a reader needs is its status: the surviving repository, Queen-MD-OLD, was archived on 20 August 2024 and is read only, its README carries a badge stating the project is not maintained, and its last code push was in April 2023. This guide records the project as it stands today, with its QR session page no longer responding, its README links still pointing at an older repository name that GitHub now reports as blocked, and its documented setup described exactly as the archived files present it.

Read the guide
Guide

Sarkar MD WhatsApp Bot: Features, Session ID, Pairing and Deployment Guide

SARKAR MD is a third party WhatsApp Multi Device bot project by Sarkar Bandaheali, built on the Baileys library and presented by its README as version 3.0.0, the Neon Edition. The first fact a reader needs is where the code can still be read: the original GitHub repository returns a 404 error today, so this guide is checked against the public fork under the miank account, whose GitHub metadata names the original repository as its parent and which carries the full README, the configuration files and a LICENSE file. Both pair code services the README links return a 404 error today and the project website listed in the repository metadata does not load, so this guide links no session service for SARKAR MD as a working service.

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