Skip to main content
Glama
Sign In
Claude Bridge

Claude Bridge

by JackLuciano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Claude Bridge

No user-submitted related servers found.

    Related Servers

    • BlenderMCP

      kjanat
      A
      license
      A
      quality
      D
      maintenance
      Connects Blender to Claude AI, enabling prompt-assisted 3D modeling, scene creation, and manipulation through natural language.
      21
      MIT

    • BlenderMCP

      KorwinTeo
      A
      license
      B
      quality
      D
      maintenance
      Connects Blender 3D to Claude AI through the Model Context Protocol, enabling prompt-driven 3D modeling, scene creation, and real-time object manipulation.
      22
      1
      MIT

    • blender-mcp

      Vertiiii
      A
      license
      A
      quality
      C
      maintenance
      Connects Blender 3D modeling software with Claude AI, enabling natural language control of 3D modeling and scene manipulation tasks.
      17
      5
      MIT

    • BlenderMCP

      Eminemminem
      A
      license
      B
      quality
      D
      maintenance
      Connects Blender to Claude AI through the Model Context Protocol, enabling AI-assisted 3D modeling, scene creation, and manipulation through natural language commands.
      17
      2
      MIT

    • BlenderMCP

      SK-DEV-AI
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude AI to Blender through the Model Context Protocol, enabling AI-assisted 3D modeling, scene creation, object manipulation, and material control. Supports downloading assets from Poly Haven and generating 3D models through Hyper3D Rodin.
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation2/5

    The set collapses to one god-tool (bl) whose sub-ops overlap heavily: property setting can be done via prop, set{props}, nodes set, or bop; movement via move, set{loc}, and apply xform; and the look tool duplicates bl's render look:true and view presets. With 50+ operations inside a single description, an agent faces constant misselection risk between import/export (listed twice, once inside fit), add vs dup vs bop, and del vs edit{delete}.

    Naming Consistency3/5

    Within bl the ops follow a consistent terse lowercase style (add, del, mat, tex, mod, con, bop, py), but the style mixes verbs (add, move, apply, aim) with bare nouns (scene, prop, col, nodes, room) and heavy abbreviations. The two top-level names don't follow a shared pattern either: 'bl' is an abbreviation while 'look' is a verb.

    Tool Count3/5

    Literally there are only 2 tools, which is thin for a Blender bridge, but the bl tool crams roughly 50+ distinct operations into one dispatch surface, so the effective API is far above the 3-15 sweet spot. The single mega-tool trades count for a massive surface, which is borderline rather than well-scoped.

    Completeness5/5

    Coverage of the Blender domain is near-total: modeling (add/edit/mod/room/curve), materials and PBR textures, assets, geometry nodes, animation and constraints, camera/lighting, viewport capture, render/export, scene checks, and escape hatches (py, bop, api) for anything not covered. There are effectively no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources