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