Humatron AI
sign up
Manus LogoBuild Manus AI Worker
build
This builder's guide provides detailed instructions for building AI Worker with Manus core agent.

TL;DR »

When using Manus as a core agent, it acts as a reasoning and execution engine for the AI worker, while Humatron provides the orchestration, infrastructure and services for the AI worker.
To integrate Manus with Humatron, you need:
  1. Create new build
  2. Select Manus as the core agent
  3. In Manus - create new Manus connector with Humatron MCP
  4. Pass newly created connector ID to Humatron build
  5. Set Manus API key to Humatron build
  6. Configure additional MCP, functions, VPS scripts, etc.
  7. Submit new build
  8. Hire the AI Worker using the new build 🚀

End-To-End Message Flow »

When user interacts with the Manus-based AI worker, the message flow is as follows:
  • User (request)Humatron
  • Humatron Manus Task
  • Manus tasks produces response
  • Manus calls Humatron MCP Connector
  • Humatron User (response)
A Manus response is only "delivered" if it goes through Humatron MCP. Replies inside Manus alone are invisible to the user. If this end-to-end loop is not closed, the AI worker is effectively silent.

One Build - Many Hires »

A Humatron build acts as a shared template for AI workers of a certain type. It defines the Manus agent configuration, custom tools, and MCP servers that are inherited by all hires of that build. When a hire is created, the build is instantiated into a unique hire instance, which is then customized further based on the employer's context and the specific job requirements.
Common build settings that are shared across all hires of the same build include:
  • Manus agent configuration
  • Role and role's instructions
  • Deployment configuration
  • Custom tools and MCP servers
Each build can be used to create multiple AI workers. When you create a build, it automatically generates a resumé - the public-facing representation of that build. Note that access to the build and its resumé is governed by the build's publishing status.
Depending on publishing status, the build will be visible either to you only, your company or to the general public. Among other parameters, the resumé displays essential information from the build such as professional summary, role description, and the list of skills.
During hiring, users select the build (via its resumé) and fill up the hiring form to create a new AI worker from that build. When fully deployed and instantiated, this newly created AI worker becomes an independent instance of that build that is customized with:
  • Personalized name and avatar
  • Social preferences
  • Communication style
  • Job-specific instructions and requirements
  • Docker environment variables
  • Shell scripts to run before and after the deployment
  • Knowledge base data sources
Combination of separate builds and hires defines Humatron's «One Build - Many Hires» architecture, where every AI worker functionally consists of two layers:
  • Build - common configuration and shared agentic capabilities
  • Hire - employer-specific, individual and job-related customizations
This two-stage approach allows to concentrate most of the capabilities in a shared build ensuring functional consistency across workers - while in the same time allowing for individual customization to meet specific employer's needs.

Step 1: Create new build »

Start a new build. Every new build at Humatron starts with the following properties:
  1. Role
    A role typically defines a job title, position or level of responsibility within a company or organization. It typically reflects the nature of the job, the industry, and sometimes the hierarchy within the workplace. Examples of roles:
    • Legal Assistant
    • Accountant
    • Document Translator
    • Python Coder
  2. Avatar
    Ensure that the build avatar matches the build's job role. Note that selecting a human image or a photograph for your AI worker build does not conceal their AI nature. Note also that if the social customization is allowed the avatar can be changed during the hiring process along with name, gender and communication style.
    NOTE:
    Avatar image must be a square of at least 96px size or larger. 512px size or larger if using Slack. 2 MB maximum file size.
  3. Role Instructions
    Role instructions acts as an LLM system prompt and provide an initial detailed operating handbook, e.g. employee handbook, for the main functional responsibilities of this AI worker. Each functional job area should be described in sufficient detail - in the same way as it would be described to a junior level human employee. These instructions will be integrated into the overall context for Manus agent and should be modelled similar to a well organized reasoning prompt.
    Note that an AI worker will learn new skills and adapt existing skills and internal instructions over time. All AI workers come with a set of built-in core skills and capabilities that are specific to the Manus agent. You do not need to instruct about any of these. Do not include function or MCP server definitions here.
    You can also attach any files that would help to augment or define additional general context about role instructions. These may include operating guidelines, technical specifications, etc.

Step 2: Configure Manus Integration »

If necessary, create new Manus project on Manus side. Select "Manus" as the core agent on build form - that will open Manus configuration form:
  • Enter Manus API key.
  • Select Manus Agent Profile from the dropdown.
  • Enter optional Manus Project ID (if it was created above).
  • Add provided instructions to your Manus global or project settings.
  • Add provided Manus MCP connector "humatron-agent-mcp" to your Manus project. This MCP connector exposes Humatron functionality to Manus agent allowing it to use built-in Humatron capabilities and access Humatron data. Note the ID of the newly added connector (you will need it on the next step).
  • Enter a comma-separated list of IDs of all MCP connectors that you want to use for this build. Note that this list should contain at least ID of the newly added MCP connector "humatron-agent-mcp" as well as IDs of all other MCP connectors added on the Manus side that you want to use for this build. If MCP connector ID is not listed here, it will not be available to the Manus-based AI worker.

Step 3: Configure Function & MCP Servers »

You can optionally add REST functions and MCP servers to your build - the additional, custom set of tools that Manus agent will have access to. These tools will be deployed for each new hire on the hire-side either on a VPS instance or on on-prem deployment.
With Manus core agent - there are four sets of tools that Manus agent has access to:
  • Manus built-in tools
  • MCP connectors you add to your Manus project
  • "humatron-agent-mcp" MCP server (part of Manus agent integration) that exposes Humatron functionality to Manus agent
  • Custom tools added and deployed on the Humatron side (build form settings)
Make sure that there are no functional conflicts or duplicates between the four sets of tools. Also ensure that there is no technical interference between different sets of tools. We recommend starting with a minimal number of custom tools and developing and testing tools in isolation outside of Humatron platform since it is not designed as a full-featured development environment.
Start Small & Increment
Ensuring conflict-free operation between multiple sets of tools is not trivial. Start with a minimal number of custom tools that you do not expect to conflict with each other. Add custom tools gradually and use agent evaluations to test. Develop and test them in isolation.

Step 4: Additional Configuration »

Each build includes a set of additional configuration options and settings. These are optional, as they are either read-only or preconfigured with sensible defaults.
  1. Restrict Social
    You can protect your distinct brand identity (personal or corporate) by restricting modifications to social attributes such as name, gender, avatar, and communication style during the hiring process. When such modifications are disabled, all AI workers built from your build will use name, gender, avatar and communication style of this build maintaining consistent social attributes of your brand.
    Important considerations:
    • This feature prevents multiple hires of the same build by a single employer, as it would create duplicate identities.
    • If you choose to restrict social attribute modifications, you must provide default values for these properties in your build configuration.
  2. Initial Shell Scripts
    Each hired AI worker is deployed either on-prem or on cloud (AWS, Azure, or OpenStack) on its own VPS instance. You can attach shell scripts to run before and after the build's MCPs are installed, enabling fine-tuned configuration of the hire instance runtime environment during startup and restarts. For example, you might use these init scripts to install additional libraries or Docker containers at startup to support custom telemetry, logging, or other extensions for your build.
  3. Deployment
    Humatron supports both on-prem and cloud-based deployments with full isolation of the infrastructure and data. On-prem deployment allows for full control of the infrastructure and data, while cloud-based deployment allows for easy scalability and deployment and management. Each AI worker is deployed either on-prem or on cloud (AWS, Azure, or OpenStack) on its own VPS instance. If you are deploying using cloud-based VPS, choose an instance that matches your CPU and RAM needs; all workers run on Ubuntu 24.04 LTS by default. Keep in mind that added MCP servers are the primary factor influencing how much CPU and memory capacity your VPS instance should provide.
  4. Support Email
    A support email is required and will be publicly displayed on the resumé as the primary support contact. Additionally, you may provide an optional link to external documentation or a detailed description of the AI worker's capabilities, skills, and functionality. This link will also be shown on the resumé.
  5. Build Token
    Each build is issued a unique build token, generated once at creation. Together with the corresponding organization and hire tokens, it can be used for MCP or tool authorization and authentication.

Step 5: Submit & Hire »

Once build form is completed - submit it. Note that you can update and reconfigure the build any time later. After submission, you can hire the AI worker right away using the new Manus-based build 🚀
NOTE:
  • Some changes to the build may require a restart of the AI worker to take effect:
    • It is recommended to assume that changes to the build will be applied to the new AI workers only.
    • When build is published on the marketplace (public) - there is no way to force a restart of the AI workers of this build.
  • Even if build has no AI workers - it will still incur minimal credit consumption.
  • Build can only be deleted after all AI workers of this build are terminated, if any.
  • When build is submitted - the resume for this build is automatically generated.