consult_geomancy — SpiritWave Labs Divination Engine MCP Tool
consult_geomancy
(consult geomancy) is one of 6 tools on the
SpiritWave Labs Divination Engine
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call consult_geomancy from your client
- Claude Code SpiritWave Labs Divination Engine consult_geomancy run in your project directory
- Claude Desktop SpiritWave Labs Divination Engine consult_geomancy ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SpiritWave Labs Divination Engine consult_geomancy ~/.cursor/mcp.json
- VS Code SpiritWave Labs Divination Engine consult_geomancy .vscode/mcp.json
- Zed SpiritWave Labs Divination Engine consult_geomancy ~/.config/zed/settings.json
- Windsurf SpiritWave Labs Divination Engine consult_geomancy ~/.codeium/windsurf/mcp_config.json
- Cline SpiritWave Labs Divination Engine consult_geomancy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SpiritWave Labs Divination Engine consult_geomancy ~/.gemini/settings.json
- Grok SpiritWave Labs Divination Engine consult_geomancy .mcp.json (in your project root)
- ChatGPT SpiritWave Labs Divination Engine consult_geomancy Settings → Connectors → Advanced → Developer mode
- Claude.ai SpiritWave Labs Divination Engine consult_geomancy Settings → Connectors → Add custom connector
- LangChain SpiritWave Labs Divination Engine consult_geomancy pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http council https://mcp.spiritwavelabs.com/mcpOther 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.