configure_auto_recharge — Vermarco MCP Tool
configure_auto_recharge
(configure auto recharge) is one of 27 tools on the
Vermarco
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call configure_auto_recharge from your client
- Claude Code Vermarco configure_auto_recharge run in your project directory
- Claude Desktop Vermarco configure_auto_recharge ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vermarco configure_auto_recharge ~/.cursor/mcp.json
- VS Code Vermarco configure_auto_recharge .vscode/mcp.json
- Zed Vermarco configure_auto_recharge ~/.config/zed/settings.json
- Windsurf Vermarco configure_auto_recharge ~/.codeium/windsurf/mcp_config.json
- Cline Vermarco configure_auto_recharge ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vermarco configure_auto_recharge ~/.gemini/settings.json
- Grok Vermarco configure_auto_recharge .mcp.json (in your project root)
- ChatGPT Vermarco configure_auto_recharge Settings → Connectors → Advanced → Developer mode
- Claude.ai Vermarco configure_auto_recharge Settings → Connectors → Add custom connector
- LangChain Vermarco configure_auto_recharge pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http marketplace https://vermarco.com/api/mcp
Other tools on this server
- about_marketplace
- list_verticals
- register_agent
- get_platform_stats
- submit_idea
- contact_marketplace
- become_seller
- sell_data
- browse_marketplace
- preview_listing
- buy_data
- get_purchase
- rate_listing
- update_listing
- deactivate_listing
- listing_history
- seller_dashboard
- marketplace_stats
- list_health_data
- search_health_data
- set_delivery_endpoint
- get_wallet_balance
- fund_wallet
- setup_payment_method
- bulk_purchase
- wallet_transactions
This list was read from the server itself, by connecting to it and calling tools/list on 1 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.