define_custom_blueprint — RackArchitect MCP MCP Tool
define_custom_blueprint
(define custom 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 define_custom_blueprint from your client
- Claude Code RackArchitect MCP define_custom_blueprint run in your project directory
- Claude Desktop RackArchitect MCP define_custom_blueprint ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RackArchitect MCP define_custom_blueprint ~/.cursor/mcp.json
- VS Code RackArchitect MCP define_custom_blueprint .vscode/mcp.json
- Zed RackArchitect MCP define_custom_blueprint ~/.config/zed/settings.json
- Windsurf RackArchitect MCP define_custom_blueprint ~/.codeium/windsurf/mcp_config.json
- Cline RackArchitect MCP define_custom_blueprint ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RackArchitect MCP define_custom_blueprint ~/.gemini/settings.json
- Grok RackArchitect MCP define_custom_blueprint .mcp.json (in your project root)
- ChatGPT RackArchitect MCP define_custom_blueprint Settings → Connectors → Advanced → Developer mode
- Claude.ai RackArchitect MCP define_custom_blueprint Settings → Connectors → Add custom connector
- LangChain RackArchitect MCP define_custom_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.