get_pin — 0DTE Confluence MCP Tool Read-only
get_pin
(get pin) is one of 32 tools on the
0DTE Confluence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_pin from your client
- Claude Code 0DTE Confluence get_pin run in your project directory
- Claude Desktop 0DTE Confluence get_pin ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor 0DTE Confluence get_pin ~/.cursor/mcp.json
- VS Code 0DTE Confluence get_pin .vscode/mcp.json
- Zed 0DTE Confluence get_pin ~/.config/zed/settings.json
- Windsurf 0DTE Confluence get_pin ~/.codeium/windsurf/mcp_config.json
- Cline 0DTE Confluence get_pin ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI 0DTE Confluence get_pin ~/.gemini/settings.json
- Grok 0DTE Confluence get_pin .mcp.json (in your project root)
- ChatGPT 0DTE Confluence get_pin Settings → Connectors → Advanced → Developer mode
- Claude.ai 0DTE Confluence get_pin Settings → Connectors → Add custom connector
- LangChain 0DTE Confluence get_pin pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http confluence https://mcp.0dteconfluence.com/mcpOther tools on this server
- get_latest_alert
- list_alert_history
- get_rails
- get_tape
- get_morning_desk
- get_market_clock
- get_skew
- get_gex_profile
- get_em
- get_rv_regime
- get_spy_qqq_divergence
- get_replay_today
- get_hist_replay
- check_alert_tradeable
- plan_robinhood_entry
- format_bracket_plan
- pro_rules_summary
- get_premium_compression_data
- get_path_risk_score
- get_cvd_liquidity
- get_vrp_divergence
- get_index_health
- get_macro_events
- get_daily_structure
- get_swing_structure
- get_lotto_friday
- get_correlation_grid
- get_cross_asset
- get_major_news
- get_yield_curve
- get_fear_greed
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.