convez.ai
MCP ServerAutomaçãoAvançado
beam-bots

BB.MCP - Servidor MCP para Robôs Beam

beam-bots/bb_mcp

Conecte robôs Beam Bots a agentes IA via MCP padrão

Ver no GitHub
BomPluginScore · de 0 a 100

Servidor Model Context Protocol que expõe robôs Beam Bots para agentes IA (Claude, agentes LLM customizados). Permite que Claude Desktop e outros clientes MCP controlem robots através de ferramentas tipadas, recursos de estado/topologia e parâmetros em tempo real, com controles de segurança integrados.

Instalação

$npx convez-ai beam-bots/bb_mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
75%
Último commit
há 2 dias
Versão
v0.3.5
Issues abertas
0
Contribuidores
2

Casos de uso

  • Controlar robôs industriais/colaborativos via Claude e agentes IA
  • Expor comandos, parâmetros e estado de robots para automação inteligente
  • Integrar robôs Beam em pipelines de IA com segurança e monitoramento

Veredito

Solução especializada e bem-arquitetada para quem trabalha com robótica e Beam Bots. Implementação sólida em Elixir com suporte robusto a MCP, mas requer familiaridade com o ecossistema Beam e robótica para máximo proveito.

README

A tradução para o português deste README ainda está na fila.

BB.MCP

CI License: Apache 2.0 Hex version badge Hexdocs badge REUSE status Ask DeepWiki

Model Context Protocol (MCP) server for Beam Bots robots.

bb_mcp lets AI agents (Claude Desktop, Claude Code, custom LLM agents) drive your BB-powered robots over the standard Model Context Protocol. Every robot you list at startup exposes its safety controls, declared commands, runtime parameters, and live state to any connected MCP client.

Status

Early. Multi-robot, no authentication — assume a trusted local or LAN environment.

Installation

Add bb_mcp to your dependencies:

def deps do
  [
    {:bb_mcp, "~> 0.1"}
  ]
end

Or run the installer:

mix igniter.install bb_mcp

Usage

List the robots to expose in config:

# config/config.exs
config :bb_mcp, robots: [MyApp.WX200, MyApp.SO101]

Start the server alongside your robots in the supervision tree:

children = [
  MyApp.WX200,
  MyApp.SO101,
  {BB.MCP.Server, transport: :streamable_http, streamable_http: [port: 4000]}
]

Or mount it in a Phoenix router (Streamable HTTP transport):

defmodule MyAppWeb.Router do
  use Phoenix.Router
  import BB.MCP.Router

  scope "/" do
    bb_mcp "/mcp"
  end
end

What gets exposed

For each robot, agents see:

Tools

Cross-cutting tools — each takes a robot string argument selecting the target robot:

ToolSource
list_robotsconfigured robots index
get_stateBB.Safety.state/1 + BB.Robot.Runtime
force_disarmBB.Safety.force_disarm/1
list_commandsBB.Dsl.Info.commands/1
list_parametersBB.Parameter.list/2
get_parameterBB.Parameter.get/2
set_parameterBB.Parameter.set/3
send_joint_positionsBB.Motion.send_positions/3
query_eventsper-session BB.PubSub ring buffer

Per-command tools (×N) — one tool per {robot, command} pair declared in each robot's Spark DSL, registered at session startup. Tool name is {robot}.{command} (e.g. wx200.home); the input schema is derived from the command's typed arguments. Dispatch goes through BB.Robot.Runtime.execute/3 + BB.Command.await/2. The built-in arm/disarm commands surface as {robot}.arm and {robot}.disarm.

Resources

  • bb://robots — index of configured robots
  • bb://robots/{robot}/topology — links, joints, sensors, actuators
  • bb://robots/{robot}/state — operational state, safety state, running commands
  • bb://robots/{robot}/joints — current joint positions and velocities
  • bb://robots/{robot}/commands — declared commands and their argument schemas
  • bb://robots/{robot}/parameters — registered parameters with current values

Licence

Apache-2.0. See LICENSES/Apache-2.0.txt.

Ver o original no GitHub

Bom para

Relacionados