Extensions

Prerequisites: Before reading this article, it is recommended to first understand the resource model described in Resources & Credentials.

Monstrum’s capability extensions are not limited to the 6 built-in resource types. Through plugins and templates, you can integrate additional external systems and reuse proven Bot configuration blueprints.

Overview

The platform offers multiple ways to extend a Bot’s external capabilities:

Method	Description
Built-in Resources	The 6 resource types that come with the platform (SSH, MCP, Bot, Web, Web3, Agent), ready to use out of the box
Platform Plugins	Officially approved plugins installed to the platform by administrators, providing new resource types (e.g., GitHub, GitLab, Notion)
Agent Plugins	Plugins that users install on their local Agent, bridging tools to the platform through the Agent
Templates	Import pre-configured Bot blueprints (YAML files) to quickly deploy complete configurations including Bots + Workflows + resource references

For built-in resource usage, see Resources & Credentials. For the plugin system (including the differences between Platform Plugins and Agent Plugins), see Plugins. For full details on the Agent, see Local Agent Integration. This article focuses on the template system and marketplaces.

Plugin Marketplace

The Plugin Marketplace displays both official and community plugins. Official plugins execute in the platform cloud, while community plugins are installed on a local Agent for execution.

In the left navigation bar, click Marketplace > Plugin Marketplace
Browse the available plugin list, using the source filter to distinguish between official and community plugins

For details, see Plugins.

Template System

Templates are portable blueprints for Bot configurations, imported and exported as YAML files. A template encapsulates:

Bot configuration (name, description, system prompt, runtime parameters)
Workflow definitions (steps, connections, variable mappings)
Resource references (declares what types of resources are needed, but does not include actual credentials)
Bot memory (manually added memory entries)

Templates do not include actual resource configurations or credentials — after installation, you need to bind your existing resources to the newly created Bot.

Exporting Templates

Export a configured Bot as a YAML template for backup or sharing:

Export a single Bot:

Go to the Bot details page
Click the Export button
Download the YAML file

Export a Bot Group:

Go to the Bot Group details page
Click the Export button
The downloaded YAML file contains the configurations for all Bots in the group

The exported YAML includes:

Bot configuration (without credentials)
Resource hints (resource_hints) — declares the original bound resource types and names
Channel hints (channel_hints) — declares the original configured channel types
Workflow definitions
Manual memory entries

Importing Templates

Create a Bot from a YAML file:

On the Template Marketplace page, click Import
Upload a .yaml or .yml file
The platform parses the template contents

Installation Wizard

Whether installing from the marketplace or importing from a file, template installation is completed through a wizard:

Step 1: Preview Contents

Review the Bots, workflows, and other components the template will create, and confirm the installation intent.

Step 2: Bind Resources

The template lists the resources it requires (resource_hints). You need to map your existing resources to these references:

Select an existing resource of the same type
Or create a new resource on the spot

Step 3: Complete Configuration

Choose an LLM provider and model for the Bot
Optionally configure messaging channels
Confirm to finalize Bot creation

After configuration, the Bot is automatically activated. You can also skip some configuration steps and complete them later on the Bot details page.

Template Marketplace

The Template Marketplace is the entry point for discovering and sharing Bot configuration blueprints, displaying both official and community templates.

In the left navigation bar, click Marketplace > Template Marketplace
Browse the available template list

The page supports:

Search: Search templates by keyword
Sort: Sort by install count / favorites / newest
Tag filter: Filter templates by tags
Source filter: Official templates / Community templates

Click a template card to view details, including:

Included Bots and workflow components
Required resource types
Install count and ratings

Click Install to enter the installation wizard (same process as above).

Official vs. Community Templates

	Official Templates	Community Templates
Source	Published by the platform team	Submitted by community users
Review	Reviewed by administrators	Community-governed (ratings, reports)
Installation	Same (wizard-based installation)	Same
Security	Templates are YAML configurations with no executable code, posing low security risk	Same

Submitting Community Templates

Share your Bot configuration with the community:

Export a YAML template from the Bot details page
Submit it to the community section in the Template Marketplace
Other users can browse, rate, and install it into their own workspace

Common Use Cases

Quickly Set Up a Specific Scenario

Install a pre-configured Bot blueprint from the Template Marketplace:

“GitHub Issue Auto-Handler” template: includes a Bot + issue handling workflow; bind your GitHub resource after installation and it’s ready to use
“Ops Patrol” template: includes a Bot + patrol workflow + scheduled triggers; bind SSH resources after installation

Share within a team:

Export the Bot as a YAML template and send it directly to team members
Members import it and bind resources following the wizard

Share with the community:

Export the Bot as a YAML template
Submit it to the community section of the Template Marketplace
Other users can discover and install it from the marketplace

Integrate Custom Tools

If the platform doesn’t have the plugin you need, you can integrate through a local Agent:

Install monstrum-agent locally
Configure the .mst plugin package or custom tools in the Agent
After the Agent connects to the platform, tools are automatically registered as resources
Bind them in the Bot’s resource configuration to start using them

For details, see Local Agent Integration.

FAQ

Bot is in draft state after template installation

After template installation, if the LLM provider and resource binding configuration are not completed, the Bot may remain in draft state. Go to the Bot details page to complete the configuration and activate it.

Imported YAML format is incorrect

Confirm that the file is a YAML template exported from Monstrum and contains the api_version: v2 header. Manually written YAML files must conform to the template format specification.

New resource type not visible after plugin installation

Confirm the plugin was installed successfully (the page shows a success message)
Refresh the resource management page
See the FAQ section in Plugins for more details

Edit this page on GitHub