Skip to main content
Glama
Mangomunchr

FARPY

by Mangomunchr
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Related Servers

Alternatives to FARPY

No user-submitted related servers found.

    Related Servers

    • blender_fleet

      Kiet1308
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI agents to concurrently submit isolated 3D modeling jobs to headless Blender workers, with per-job outputs, logs, and status tracking.
      MIT

    • rupa3d

      tiranyx
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to perform 3D asset creation and verification: exact b-rep CAD, GLB validation with embedded certificates, mesh inspection, and physics scenes, with most tools running without Blender.
      36
      81 npm
      MIT

    • Blender-MCP

      soozs1
      A
      license
      Not graded
      quality
      C
      maintenance
      BlenderMCP connects Blender to AI agents via the Model Context Protocol, enabling direct 3D object manipulation, material application, asset downloads, and Python code execution with secure token-authenticated local communication.
      MIT

    • mcp-3d-modeling-agent

      SekaiNoOwari77
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that exposes 218 Blender tools for full 3D modeling pipelines, with a LangGraph agent layer for planning, executing, observing, and reviewing modeling tasks with evidence-based verification.
      218
      AGPL 3.0
    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

    A3.6/5.0

    Scored across 6 tools

    Disambiguation3/5

    Most tools are distinct, but inspect and quote both create quote-like objects and both explicitly do not spend, making their boundary fuzzy. Status, download, start, and receipt are clearly separated.

    Naming Consistency3/5

    Names are simple, lowercase, and single-word, but they mix imperative verbs (inspect, start, download) with noun-style actions (status, receipt). There is no consistent verb_noun pattern, though the names remain readable.

    Tool Count5/5

    Six tools is well-scoped for the quote-to-receipt rendering workflow. Each tool represents a meaningful stage in the process without redundant or unnecessary surface area.

    Completeness4/5

    The core lifecycle is covered: inspect, quote, start, status, download, and receipt. Minor gaps exist such as no explicit cancel/refund flow and upload is only referenced via upload_id, but agents can work around these for typical jobs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources