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