get_device_blueprint — RackArchitect MCP MCP Tool Read-only
get_device_blueprint
(get device blueprint) is one of 12 tools on the
RackArchitect MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_device_blueprint from your client
- Claude Code RackArchitect MCP get_device_blueprint run in your project directory
- Claude Desktop RackArchitect MCP get_device_blueprint ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RackArchitect MCP get_device_blueprint ~/.cursor/mcp.json
- VS Code RackArchitect MCP get_device_blueprint .vscode/mcp.json
- Zed RackArchitect MCP get_device_blueprint ~/.config/zed/settings.json
- Windsurf RackArchitect MCP get_device_blueprint ~/.codeium/windsurf/mcp_config.json
- Cline RackArchitect MCP get_device_blueprint ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RackArchitect MCP get_device_blueprint ~/.gemini/settings.json
- Grok RackArchitect MCP get_device_blueprint .mcp.json (in your project root)
- ChatGPT RackArchitect MCP get_device_blueprint Settings → Connectors → Advanced → Developer mode
- Claude.ai RackArchitect MCP get_device_blueprint Settings → Connectors → Add custom connector
- LangChain RackArchitect MCP get_device_blueprint pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http rack-architect-mcp https://mcp.rackarchitect.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.