mint_eligibility_session — upgrade agent MCP Tool
mint_eligibility_session
(mint eligibility session) is one of 19 tools on the
upgrade agent
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mint_eligibility_session from your client
- Claude Code upgrade agent mint_eligibility_session run in your project directory
- Claude Desktop upgrade agent mint_eligibility_session ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor upgrade agent mint_eligibility_session ~/.cursor/mcp.json
- VS Code upgrade agent mint_eligibility_session .vscode/mcp.json
- Zed upgrade agent mint_eligibility_session ~/.config/zed/settings.json
- Windsurf upgrade agent mint_eligibility_session ~/.codeium/windsurf/mcp_config.json
- Cline upgrade agent mint_eligibility_session ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI upgrade agent mint_eligibility_session ~/.gemini/settings.json
- Grok upgrade agent mint_eligibility_session .mcp.json (in your project root)
- ChatGPT upgrade agent mint_eligibility_session Settings → Connectors → Advanced → Developer mode
- Claude.ai upgrade agent mint_eligibility_session Settings → Connectors → Add custom connector
- LangChain upgrade agent mint_eligibility_session pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http upgrade-agent https://www.upgradeagent.ai/api/mcpOther tools on this server
- check_upgrade_eligibility
- start_eligibility_check
- get_eligibility_result
- place_bid
- modify_bid
- get_bid_status
- get_price_breakdown
- cancel_bid
- predict_bid_success
- start_watch
- get_watch_status
- ask_upgrade_agent
- partner_question_insights
- usage_totals
- list_partners
- get_partner_info
- get_upgrade_pricing
- search_upgrade_options
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.