figjam-context-mcp
Related Servers
Alternatives to figjam-context-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables AI agents to read, inspect, and export Figma designs programmatically. Provides tools for listing components, styles, and exporting assets in various formats.51-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to visualize tasks on a collaborative Sketchbord whiteboard by composing content into diagrams, editing them incrementally, and reading back the board including user-drawn additions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.505 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically interact with a Miro board through the Miro API, supporting operations like creating items, updating positions, and managing connectors.16ISC
- AlicenseAqualityAmaintenanceEnables reading GitHub Projects v2 kanban boards mid-conversation, with tools to list boards, retrieve board details, and summarize their contents.359 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceEnables MCP-compatible LLMs to interact with Miro whiteboards to manage boards, create and manipulate shapes, and organize content through grouping tools.-
TDQS
Scored across 5 tools
Each tool maps to a distinct role: ingest (fetch snapshot), read/summarize (get_board_context), specific Q&A (answer_from_board), compare snapshots (diff_board), and config self-test (diagnose_llm_config). The main risk area is get_board_context vs answer_from_board, which both read from the same snapshot; the descriptions spend a lot of text partitioning them (summaries vs single factual questions), which mostly resolves the overlap but shows the boundary is not self-evident.
All names are snake_case and verb-first (ingest_board, get_board_context, answer_from_board, diff_board, diagnose_llm_config). The verbs vary in form (plain verb, verb_prepositional, verb_object_object), but the pattern remains readable and predictable.
Five tools is well-scoped for a board-snapshot context server: one write path, two read paths, one comparison, one diagnostics. No tool appears redundant or bolted on.
The lifecycle is covered: ingest, summarized/structured reading with cursors and search, targeted Q&A, snapshot diffing, and model diagnostics. Minor gaps exist around snapshot management (no explicit list/delete/prune of the bounded local history or snapshot inventory), but compareTo and re-ingest let agents work around these.