Quickstart

You need Claude (claude.ai, the Claude Desktop app or Claude Code) and a Speed sign-in. You don't need to set anything up first: the prompt walks you through connecting Speed if it isn't connected yet.

1. 1Step 1: Copy the Speed prompt

   Click Copy prompt. It copies the whole prompt below.

   The Speed prompt · paste it into Claude with nothing else

   Download .mdCopy prompt

   You are going to design hardware with me in Speed, a CAD app that runs in my browser. I'm not an engineer and I'm in a hurry, so keep every message short and plain. No headings.
   
   STEP 1. CONNECT. Check whether you have Speed's tools (status, plan, add_parts, run_physics_check, run_fea).
   If you have them, go to step 2. If not, send me only the steps for the app you are running in, then stop until I say "done":
   - claude.ai or the Claude Desktop app:
     1. Go to Customize → Connectors (older versions: Settings → Connectors).
     2. Click + Add → Add custom connector.
     3. Name: Speed. URL: https://app.tryspeed.ai/mcp
     4. Click Continue, then Add. Leave the detected sign-in settings as they are: no API key, no client ID, no secret.
     5. Click Connect. On the Connect Speed page, sign in if asked, then click Allow.
     6. Under Tool permissions, set Read-only tools and Write/delete tools to Always allow.
     7. In this chat, click + (bottom left) → Connectors → check Speed is on. Then say "done".
   - Claude Code:
     1. Type /exit, then run this in your terminal: claude mcp add --transport http speed https://app.tryspeed.ai/mcp
     2. Start claude again, type /mcp, choose speed → Authenticate, and click Allow in the browser.
     3. Paste this prompt again.
   - Any other app: send me https://tryspeed.ai/docs/connect and stop.
   If I say "done" and you still can't see the tools, tell me to start a new chat with Speed switched on and paste this prompt again.
   
   STEP 2. OPEN MY SPEED TAB. Call status. If no tab is connected, send me the app link it returns and say: "Open this link (any browser), sign in if asked, then say done." Wait, then call status again.
   
   STEP 3. ASK ONCE. Ask me exactly: "What do you want to build?" (skip it if I already said). Ask nothing else, ever. Then call enrich_request with my words and show me the brief in a few lines: what I asked, what you assumed (I may change any value), what you'll check. Choose sensible defaults for everything I didn't say. If part of my idea would be a weapon or would bring something down, build the non-destructive part (detection, sensing, structure, power) and say so in one line.
   
   STEP 4. BUILD FAST, one subsystem at a time, following Speed's rules:
   - Call new_design first (never delete the parts of the design that's open), then plan, marking every requirement stated or assumed.
   - Build from scratch with Speed's kits (add_kit) and detailed parts (add_part with a detail from part_library), one subsystem at a time, in the order the load flows: structure, then drive, then what it carries. Use a ready-made product (load_product) only if I ask for one by name.
   - Use real parts: search_catalogue, then swap_part. Say so when nothing in the catalogue fits.
   - After each stage call run_physics_check, fix what fails (two tries at most), then view_model to look.
   - When the design carries loads, call set_load_cases with each load named (for example "Hard landing, 3 g"), then run_fea.
   - Don't narrate between tool calls.
   
   STEP 5. FINISH: call save_project, then reply in eight short lines at most: what you built, the key numbers (mass, the main performance figure, the lowest safety factor), the verdict, and every assumption. Never call it verified, certified or flight-ready: Speed's checks and FEA are screening grade, for an engineer to review. Then offer exactly these next steps:
   - Run FEA for a 3 g landing
   - Swap the motors for the next size up and compare
   - Make the one-pager

2. 2Step 2: Paste it into Claude

   Open claude.ai, the Claude Desktop app or Claude Code. Start a new chat, paste the prompt and send it.

   If Speed isn't connected yet, Claude replies with the connect steps for the app you're in. Follow them exactly. On claude.ai that means Customize → Connectors → + Add → Add custom connector, with the name Speed and this URL, then Continue → Add → Connect → Allow:

   Connector URLCopy

   https://app.tryspeed.ai/mcp

   Then say done. In Claude Code, you paste the prompt again after the restart. The full steps for every app are on Connect your AI app.

3. 3Step 3: Follow it

   Claude checks the connection. If no Speed tab is open, it sends you a link. Open the link (any browser works: it connects whichever one opens it), sign in, and say done.

   Claude then asks one question: What do you want to build? Answer in one sentence, for example:

   Type thisCopy

   A 6-inch long-range quadcopter for about 20 minutes of flight, carrying a 150 g camera.

   Switch to your Speed tab and watch. Claude builds one subsystem at a time, checks each one, and ends with a short summary in the chat.

What you'll see#

• In Speed: the bar at the top says Connected to Claude. The Agent panel shows Claude's plan, then one step for every tool call.
• On the canvas: the frame appears first, then the motors and propellers, then the battery and electronics, then the payload.
• In the chat: a few short lines at the end with the mass, the main performance figure, the lowest safety factor, the verdict, and every value Claude assumed.
• Three suggested next steps: run FEA for a 3 g landing, swap the motors for the next size up and compare, and make the one-pager.

How long it takes#

• Connecting Speed the first time: about two minutes.
• A first build on claude.ai: typically 2 to 5 minutes, depending on how big the design is.
• A follow-up, such as an FEA run, a part swap or the one-pager: typically 1 to 3 minutes.

Next steps#

Something unclear or wrong? Tell us at support@tryspeed.ai.