get_studio — House Duck MCP Tool Read-only
get_studio
(get studio) is one of 1 tool on the
House Duck
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_studio from your client
- Claude Code House Duck get_studio run in your project directory
- Claude Desktop House Duck get_studio ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor House Duck get_studio ~/.cursor/mcp.json
- VS Code House Duck get_studio .vscode/mcp.json
- Zed House Duck get_studio ~/.config/zed/settings.json
- Windsurf House Duck get_studio ~/.codeium/windsurf/mcp_config.json
- Cline House Duck get_studio ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI House Duck get_studio ~/.gemini/settings.json
- Grok House Duck get_studio .mcp.json (in your project root)
- ChatGPT House Duck get_studio Settings → Connectors → Advanced → Developer mode
- Claude.ai House Duck get_studio Settings → Connectors → Add custom connector
- LangChain House Duck get_studio pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http house-duck-public https://bbgwvpwzkyudbtcgrbtm.supabase.co/functions/v1/house-duck-mcp
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.