Skip to main content
Glama
nashirabbash

CoppeliaSim MCP Server

by nashirabbash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CoppeliaSim MCP Server

No user-submitted related servers found.

    Related Servers

    • robosimtools-mcp

      RahulRajelli
      A
      license
      A
      quality
      D
      maintenance
      Exposes 12 robotics/simulation tools from robosimtools.com as MCP tools, enabling AI agents to perform conversions (quaternion, URDF, MJCF), validation, and CAD imports locally.
      12
      1
      MIT

    • MuJoCo MCP Server

      Rongxuan-Zhou
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes MuJoCo physics simulation to AI assistants via 65 MCP tools, enabling natural language control of robotics simulation, trajectory optimization, contact analysis, and video export.
      9
      MIT

    • coppeliasim-mcp

      KevinInoCol
      A
      license
      B
      quality
      A
      maintenance
      An MCP server that lets Claude Code or any MCP client drive a running CoppeliaSim 4.10 simulation--building scenes, moving objects, creating joints and proximity sensors, running simulations, and reading sensors--without exposing arbitrary Lua execution.
      31
      1
      MIT

    • openscad-mcp

      jkoets
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to create and manipulate 3D models using OpenSCAD through MCP tools for code-based modeling, preview, and export.
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 18 tools

    Disambiguation3/5

    Most tool families are distinct (scene, sensors, ROS 2, mechanisms, physics), but coppelia_step is a mega-tool that can execute arbitrary simulator code and overlaps with simulate, motion, trajectory, sensors, imports, and scene operations. Close pairs like experiments vs. physics_benchmark and ros2 vs. ros2_status further blur boundaries, though descriptions provide guidance.

    Naming Consistency5/5

    All tools use the same coppelia_ prefix and lower snake_case style, making names predictable and easy to scan. The mix of noun-like and verb-like stems (scene, health, step, import_model) is still consistent with the namespace convention.

    Tool Count3/5

    At 18 tools, the server is in the borderline-heavy range for a single MCP surface. While the domain is broad, several tools overlap in practice, and some pairs could likely be consolidated without losing capability.

    Completeness5/5

    The surface covers execution, simulation stepping, scene save/load, model and floorplan import, sensors, motion planning/IK, trajectory execution, ROS 2 integration, datasets, experiments, physics engine configuration, signals, and health checks. No obvious lifecycle gap remains for a CoppeliaSim robotics simulation server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources