bedroom_air_checkup — HouseExhale MCP Prompt
bedroom_air_checkup
is one of 1 prompt on the
HouseExhale
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke bedroom_air_checkup from your client
- Claude Code HouseExhale Prompt/bedroom_air_checkup run in your project directory
- Claude Desktop HouseExhale Prompt/bedroom_air_checkup ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HouseExhale Prompt/bedroom_air_checkup ~/.cursor/mcp.json
- VS Code HouseExhale Prompt/bedroom_air_checkup .vscode/mcp.json
- Zed HouseExhale Prompt/bedroom_air_checkup ~/.config/zed/settings.json
- Windsurf HouseExhale Prompt/bedroom_air_checkup ~/.codeium/windsurf/mcp_config.json
- Cline HouseExhale Prompt/bedroom_air_checkup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HouseExhale Prompt/bedroom_air_checkup ~/.gemini/settings.json
- Grok HouseExhale Prompt/bedroom_air_checkup .mcp.json (in your project root)
- ChatGPT HouseExhale Prompt/bedroom_air_checkup Settings → Connectors → Advanced → Developer mode
- Claude.ai HouseExhale Prompt/bedroom_air_checkup Settings → Connectors → Add custom connector
- LangChain HouseExhale Prompt/bedroom_air_checkup pip install langchain-mcp-adapters
HouseExhale also offers 5 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 22 October 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.