Figwright MCP lets coding agents work with Figwright from Cursor, Claude, and other MCP clients. The canonical install command, auth notes, and source live on the Figwright MCP listing—copy that value rather than guessing a package name.

This walkthrough is the setup spoke for that listing: client steps, permissions, and how to confirm the server is actually connected. If you searched for figwright mcp or figwright github, start on the listing, then come back here for the client checklist.

What Figwright MCP is

Figwright is an MCP server, not an agent skill. MCP servers expose tools the client can call; skills shape how the agent works a task. Use the listing for tool count, transport, and whether auth is required.

Install command

Open Figwright MCP and copy the live install or connection command. Upstream packages change—the listing and the linked source repository are the final check, including any GitHub path shown there.

Client setup

1. Confirm Node (or Docker, if the listing uses a container) is available where your MCP client runs.
2. Paste the listing command into Cursor, Claude, VS Code, or Codex MCP settings.
3. Add any API key or token the listing marks as required. Prefer a scoped or test credential.
4. Restart MCP in the client, then ask the agent to list Figwright tools and run one read-only action.

Caveats

• Do not invent extra flags or a different package than the listing shows.
• Treat write tools as opt-in. Prove a read-only call first.
• If GitHub is the source of truth, re-check the repository linked from the listing before you ship a setup to a team.

When to choose something else

Need Figma file access instead? See Figma MCP Bridge and the Figma MCP Bridge setup guide. Travel or itinerary tools: Wanderlog MCP. Browse the full MCP servers list or read which MCP clients Bowora documents.

Related: Figwright MCP listing, Wanderlog MCP setup, Ghidra MCP setup, and the MCP servers list.