Skip to main content
Glama
affinity-mcp

affinity-mcp

by StevenJPx2

Related Servers

Alternatives to affinity-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      A
      maintenance
      Enables MCP clients to inspect and modify SketchUp models through a local authenticated bridge, covering entity creation and editing, geometry, materials, tags, cameras, scenes, transactions, snapshots, and file or view export. It also offers an optional full SketchUp Ruby API execution channel and batch operations for furniture, architectural, and analysis tasks.
      37
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and modify the currently open Figma design file through a paired local Figma plugin, supporting operations like creating nodes, editing properties, and exporting PNG/SVG.
      214 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables local MCP-capable assistants to connect to Figma Desktop to read documents, pages, and selections, edit native layers and components, and export PNG/SVG across multiple files without Figma API keys.
      2
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Drives a running FigCraft desktop app through its local control channel, letting MCP clients inspect and edit documents, run menu-level commands, and capture screenshots with live UI feedback. It also exposes a Figma-compatible tool surface so existing Figma workflows and prompts can drive FigCraft unchanged.
      24
      GPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.
      10
      808 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action targets, such as document lifecycle, settings, export, and rendering. The main overlap is in the SDK/scripting cluster, where add_sdk_hint, search_sdk_hints, read_sdk_documentation_topic, report_sdk_issue, save_script_to_library, and execute_script require careful reading to distinguish.

    Naming Consistency4/5

    All tools use the affinity_ prefix with snake_case, giving a predictable namespace and mostly verb_noun naming. A few standalone operations like affinity_status and affinity_open are minor deviations but remain readable.

    Tool Count3/5

    The 22-tool surface is broad but feels heavy for the core purpose. While each tool has a plausible role, the scripting and SDK documentation tools push the count into a crowded range.

    Completeness4/5

    The set covers connection, document creation/open/listing, settings, export, basic shape/text/image insertion, rendering, and scripting/SDK support. Gaps remain around closing/deleting documents and deeper layer/selection editing, but execute_script provides a workaround.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues