get_builder_upgrade_link — solar home incentives MCP Tool Read-only
get_builder_upgrade_link
(get builder upgrade link) is one of 12 tools on the
solar home incentives
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_builder_upgrade_link from your client
- Claude Code solar home incentives get_builder_upgrade_link run in your project directory
- Claude Desktop solar home incentives get_builder_upgrade_link ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor solar home incentives get_builder_upgrade_link ~/.cursor/mcp.json
- VS Code solar home incentives get_builder_upgrade_link .vscode/mcp.json
- Zed solar home incentives get_builder_upgrade_link ~/.config/zed/settings.json
- Windsurf solar home incentives get_builder_upgrade_link ~/.codeium/windsurf/mcp_config.json
- Cline solar home incentives get_builder_upgrade_link ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI solar home incentives get_builder_upgrade_link ~/.gemini/settings.json
- Grok solar home incentives get_builder_upgrade_link .mcp.json (in your project root)
- ChatGPT solar home incentives get_builder_upgrade_link Settings → Connectors → Advanced → Developer mode
- Claude.ai solar home incentives get_builder_upgrade_link Settings → Connectors → Add custom connector
- LangChain solar home incentives get_builder_upgrade_link pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http solar-home-incentives https://api.energyaisolution.com/mcp/solarOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.