size_a_powertrain — ThrustLab MCP Prompt
size_a_powertrain
is one of 1 prompt on the
ThrustLab
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke size_a_powertrain from your client
- Claude Code ThrustLab Prompt/size_a_powertrain run in your project directory
- Claude Desktop ThrustLab Prompt/size_a_powertrain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ThrustLab Prompt/size_a_powertrain ~/.cursor/mcp.json
- VS Code ThrustLab Prompt/size_a_powertrain .vscode/mcp.json
- Zed ThrustLab Prompt/size_a_powertrain ~/.config/zed/settings.json
- Windsurf ThrustLab Prompt/size_a_powertrain ~/.codeium/windsurf/mcp_config.json
- Cline ThrustLab Prompt/size_a_powertrain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ThrustLab Prompt/size_a_powertrain ~/.gemini/settings.json
- Grok ThrustLab Prompt/size_a_powertrain .mcp.json (in your project root)
- ChatGPT ThrustLab Prompt/size_a_powertrain Settings → Connectors → Advanced → Developer mode
- Claude.ai ThrustLab Prompt/size_a_powertrain Settings → Connectors → Add custom connector
- LangChain ThrustLab Prompt/size_a_powertrain pip install langchain-mcp-adapters
ThrustLab also offers 3 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.