cursor-talk-to-figma-mcp tested by Argusic Runner
Attempt 1 of 3 · Runs with mocks · Argusic Score 92.0 of 100
all runs of cursor-talk-to-figma-mcpagentagenticagentic-aiaiai-agentsautomation
Session recording
Download the original recording · fingerprint 6e4637526ec99b03...
What the test found
Dependencies installed, the project builds with tsup, the WebSocket relay starts on port 3055, and the MCP server starts on stdio, initializes, connects to the relay, and responds to all MCP protocol messages (initialize, tools/list, prompts/list, tools/call).
Bun was not pre-installed; installed via npm --prefix to home dir. The project builds and runs. The MCP server initializes correctly over stdio, connects to the WebSocket relay, and exposes all 50+ tools and 6 prompts. Full end-to-end verification requires a real Figma environment (plugin host + active document) which is unavailable in this container.
Argusic installed cursor-talk-to-figma-mcp in 6 minutes and launched it; verification reached Verified with mock services.
Runs with mocksall runs of cursor-talk-to-figma-mcp
This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.
Error and fix timeline
No errors were recorded for this run.