Skip to main content
Version: Latest

Integrations Overview

Brobot can be integrated with various external tools and services to extend its automation capabilities beyond traditional GUI automation.

Available Integrations​

MCP Server (Model Context Protocol)​

EXPERIMENTAL FEATURE - USE WITH CAUTION

The MCP Server is an experimental, untested proof-of-concept. It is provided for research, prototyping, and exploration purposes only.

DO NOT use in production environments.

Key Warnings:

  • No comprehensive testing has been performed
  • APIs and interfaces may change without notice
  • Security vulnerabilities may exist
  • Performance and stability not guaranteed
  • Limited error handling and recovery mechanisms
  • Documentation may not reflect current implementation

By using this feature, you acknowledge these risks and agree to use it for experimental purposes only.

Enable AI agents to control Brobot automations through a RESTful API. This integration allows Large Language Models (LLMs) like GPT-4, Claude, and others to:

  • Observe application states with screenshots
  • Execute GUI automation actions
  • Make intelligent decisions based on visual feedback

Learn more about MCP Server →

info

The MCP Server is an experimental proof-of-concept. For production automation, please use the core Brobot framework directly with the standard API.

Potential Future Integrations​

The Brobot ecosystem could be extended with additional integrations. Possible areas include:

  • IDE Plugins: Visual Studio Code and IntelliJ IDEA extensions for development workflow
  • CI/CD Tools: Jenkins, GitHub Actions, and GitLab CI pipeline integration
  • RPA Platforms: Connectors for UiPath, Automation Anywhere, and Blue Prism
  • Monitoring Tools: Observability with Datadog, New Relic, and Prometheus
  • Cloud Services: AWS, Azure, and Google Cloud automation capabilities
NOT YET IN DEVELOPMENT

These integrations do not currently exist and are not in active development. If you're interested in building integrations, we welcome contributions! Open a GitHub discussion to explore possibilities.

Proposed Integration Architecture​

Future Brobot integrations will follow a consistent architectural pattern:

External Tool → Integration Layer → Brobot Core → Target Application

This design pattern will ensure:

  • Consistency: All integrations use the same Brobot state management system
  • Reliability: Brobot's well-tested automation engine (5,600+ tests, 95%+ pass rate) handles all actions
  • Flexibility: New integrations can be added without modifying core functionality
  • Maintainability: Clear separation of concerns between integration and core layers
CORE CONCEPTS

To build integrations, you'll need to understand Brobot's core concepts:

Getting Started​

Choose Your Approach​

For Experimentation & Research:

  • Try the MCP Server (experimental, AI-driven automation)
  • Perfect for prototyping AI agents that control GUI applications
  • Not suitable for production use

For Production Automation:

For Building Custom Integrations:

Contributing​

Want to build a new integration? We welcome contributions!

To contribute an integration:

  1. Review the proposed architecture above
  2. Open a GitHub discussion to discuss your integration idea
  3. See the general Contributing Guide for code standards

Help us improve the MCP Server! If you're interested in AI-driven automation, we especially welcome:

  • Bug reports and testing feedback
  • API improvements and suggestions
  • Documentation enhancements
  • Example use cases and integrations