"iRobot" matching MCP servers:

Enables agents to work with Robot Framework by discovering tests and resources, drafting tests from requirements, dry-running and executing suites, and parsing output.xml results.

Provides deterministic system information and developer utilities including date/time operations, OS details, math calculations, random data generation, hashing, text formatting, data validation, encoding/decoding, and log analysis.

A one-command MCP server that bridges a ROBOT.md file to any MCP-aware agent, exposing structured robot manifest resources and validation tools without configuration.

LLM routing proxy that cuts API costs 60-90% by auto-selecting the cheapest capable model across OpenAI, Anthropic, and Google. Provides stats, config, and model comparison tools via MCP.

A local MCP server that parses Robot Framework output.xml files, scores and groups failures, and exposes structured triage data to Claude Desktop and Claude Code.

Enables agents to search pinned robotics code and reusable task findings across frameworks, inspect provenance and requirements, and prepare supported upstream sources via recipes without executing robot code.

Puts a single OAuth 2.1 authorization gateway in front of self-hosted MCP servers, letting Claude.ai and other OIDC-backed clients sign users in and receive tokens scoped to one person and one service. Wraps stdio or Streamable HTTP upstreams behind one hostname with a path per service, with allowlisted redirects, hashed stored tokens, and per-tool audit lines.

Exposes a robot twin's catalog as LLM tools, enabling agents to query variables, run robot operations, and own task boundaries through begin_task and end_task.