dice_browse — Dice MCP Tool
dice_browse
(dice browse) is one of 44 tools on the
Dice
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call dice_browse from your client
- Claude Code Dice dice_browse run in your project directory
- Claude Desktop Dice dice_browse ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Dice dice_browse ~/.cursor/mcp.json
- VS Code Dice dice_browse .vscode/mcp.json
- Zed Dice dice_browse ~/.config/zed/settings.json
- Windsurf Dice dice_browse ~/.codeium/windsurf/mcp_config.json
- Cline Dice dice_browse ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Dice dice_browse ~/.gemini/settings.json
- Grok Dice dice_browse .mcp.json (in your project root)
- ChatGPT Dice dice_browse Settings → Connectors → Advanced → Developer mode
- Claude.ai Dice dice_browse Settings → Connectors → Add custom connector
- LangChain Dice dice_browse pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dice https://gateway.pipeworx.io/dice/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- company_register_search
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- archive_evidence
- archive_compare
- research_row
- classify_row
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- dice_cities
- dice_event
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 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.