Skip to main content
Glama
ecestnrkl

figjam-context-mcp

by ecestnrkl

Related Servers

Alternatives to figjam-context-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      Enables AI agents to read, inspect, and export Figma designs programmatically. Provides tools for listing components, styles, and exporting assets in various formats.
      5
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect Figma design files by fetching file summaries, page structures, specific nodes, and rendered image previews, along with signed-in user details and file comments. It lets agents review design feedback and explore frames, components, and layers without downloading full node trees.
      28 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to programmatically interact with a Miro board through the Miro API, supporting operations like creating items, updating positions, and managing connectors.
      16
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables reading GitHub Projects v2 kanban boards mid-conversation, with tools to list boards, retrieve board details, and summarize their contents.
      3
      168 PyPI
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible LLMs to interact with Miro whiteboards to manage boards, create and manipulate shapes, and organize content through grouping tools.
      -

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct and non-overlapping purpose: ingest_board adds a board, get_board_context retrieves its context, and answer_from_board answers questions. No ambiguity in intent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: 'ingest_board', 'get_board_context', 'answer_from_board'. The naming pattern is uniform and predictable.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to a specific workflow (ingest, context, answer). Each tool serves a necessary step without unnecessary bloat.

    Completeness4/5

    The server covers the core workflow of ingesting a board, retrieving context, and answering questions. A minor gap is the lack of a tool to list or delete ingested boards, but this may be out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues