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