To use your n8n workflows as tools inside Claude Code, add an MCP Server Trigger node, connect a tool node to it over the ai_tool connection, and activate the workflow. Then point Claude Code at the SSE endpoint: on n8n 2.29 with a v1 MCP Server Trigger the URL is http://host:5678/mcp/{path}/sse, not /mcp/{path} (that 404s). Register it with claude mcp add --transport sse. Separate concern: n8n-as-a-server (this post) is the opposite of czlonkowski/n8n-mcp, which lets Claude build workflows for you.
To keep Claude Code out of your .env, permissions.deny (Read(./.env)) stops the honest mistakes — the Read tool and a literal cat .env — but it is a string match, so node -e readFileSync('.env') or a filename assembled from fragments reads right through. A PreToolUse hook catches the script but still falls to the assembled name. Only the sandbox (sandbox.enabled with sandbox.filesystem.denyRead, Claude Code v2.1.187+) blocks every bypass at the OS level with EPERM. Ranking: sandbox > hook > deny. deny is a mistake-guard, not a security boundary.
A Claude Code slash command isn't a shortcut — it's a decision you stopped re-explaining, and the valuable part of it is the safety rules baked inside, not the instruction.
A screenshot gives Claude something to look at; measurements give it something to prove. When a bug isn't visual — like a horizontal scroll — measure the layout in the console and hand the numbers over as a structured prompt ('don't infer, use these measurements, tell me the rule then fix'). That prompt pattern, not the script, is the reusable part.
Figma AI credits are a per-seat monthly allowance (3,000 on Professional, 500 on Starter) that resets each month and doesn't roll over. Cheap actions like background removal cost a few credits; Figma Make and image generation can burn far more. When you run out, you wait for the reset or buy more at $0.03/credit. Run your own usage through the calculator below before you worry.