Run your own bot workers for mcord

Keep the bot process on infrastructure you control

A developer can deploy a bot worker on a chosen server or runtime and maintain that process independently. This makes it possible to match bot operations to an existing development and deployment workflow.

The boundary is important: the independently hosted component is the bot worker. mcord itself is not being presented as a fully self-hosted community platform.

• Node.js or Python bot workers
• Developer-controlled worker hosting and deployment
• mcord connection through REST and Gateway interfaces

Connect event-driven and request-based workflows

Gateway connectivity can support a worker that responds to activity as it occurs, while REST interfaces support request-based interaction with mcord capabilities exposed to bots.

The bot's exact behavior remains part of the developer's implementation, allowing each community to automate the tasks that actually match its workflow.

Treat bot operations as a maintained service

Because the worker runs outside mcord, its operator is responsible for deployment, availability, logs, dependencies, and keeping its credentials protected. A failed or stopped worker cannot perform its automation until it is restored.

Community roles and permissions should still be planned carefully so a bot is used only in the spaces and workflows intended for it.