CapSolver MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPSOLVER_API_KEY | Yes | Your CapSolver API key required to authenticate requests. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| solve_captchaA | Solve a captcha in token mode — no browser required. CapSolver will create a task on its server, solve the captcha challenge, and return the solution token. Use this when you only need the token to submit to a target website (e.g. via form POST or API call). Args: captcha_type: One of "reCaptchaV2", "reCaptchaV3", "cloudflare". website_url: The full URL of the page where the captcha appears. website_key: The site key / public key / data-sitekey of the captcha widget. version: reCAPTCHA version hint ("v2" or "v3"). Usually auto-detected. page_action: reCAPTCHA v3 action name (e.g. "login", "submit"). min_score: reCAPTCHA v3 minimum score threshold (0.0–1.0). invisible: Whether the reCAPTCHA widget uses invisible mode. enterprise: Whether to use the Enterprise API variant. s_token: Enterprise s_token for stoken-based verification. cdata: Cloudflare Turnstile custom data parameter. proxy: Proxy in "user:pass@host:port" or "host:port" format. user_agent: Custom User-Agent string to use during solving. timeout: Maximum seconds to wait for a solution (default: 120). polling_interval: Seconds between status polls (default: 5). Returns: {"success": True, "solution": {...}} on success. {"success": False, "error": "...", "error_id": ..., "error_code": "...", "http_status": ...} on failure. |
| detect_captchasA | Detect which captcha types are present on a given page URL. Opens the page in a headless browser and inspects the DOM to identify captcha widgets (reCAPTCHA, Cloudflare Turnstile). Requires playwright to be installed. Args: page_url: The full URL of the page to inspect. Returns: {"success": True, "url": "...", "detected_captchas": ["reCaptchaV2", ...]} on success. {"success": False, "error": "..."} on failure. |
| solve_on_pageA | Detect, solve, and optionally autofill all captchas on a page. One-shot operation: opens the page in a headless browser, detects captcha widgets, solves them via the CapSolver API, and injects the solution tokens back into the page DOM. Requires playwright to be installed. Args: page_url: The full URL of the page containing captchas. autofill: If True, inject solved tokens into the page (default: True). timeout: Maximum seconds to wait per captcha (default: 120). polling_interval: Seconds between status polls (default: 5). Returns: {"success": True, "url": "...", "results": [{"captcha_type": "...", "solved": true, "token": "...", "filled": true}, ...]} {"success": False, "error": "..."} on failure. |
| get_balanceA | Get the current CapSolver account balance. Returns: {"success": True, "balance": 5.67, "packages": [...]} on success. {"success": False, "error": "...", "error_id": ..., "error_code": "..."} on failure. |
| get_supported_captchasA | List all captcha types supported by this CapSolver instance. Returns the registered handler names and all available captcha type values. No parameters required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: solve_captcha is token-only solving from provided parameters, detect_captchas only inspects a page, solve_on_page combines detection/solving/autofill, get_balance and get_supported_captchas are utility queries. There is no meaningful overlap that would cause misselection.
All tool names follow a consistent snake_case verb_noun pattern (solve_captcha, detect_captchas, solve_on_page, get_balance, get_supported_captchas). The pattern is predictable and uniform, with no mixed conventions or vague verbs.
Five tools is well-scoped for a captcha-solving server: one core solving tool, one detection tool, one combined page-solving tool, and two informational tools. Each tool earns its place and the count fits comfortably within the ideal 3-15 range.
The tool surface covers the full user-facing workflow: checking balance, listing supported captcha types, detecting captchas on a page, solving a captcha for a token, and solving+autofilling on a page. There are no obvious dead ends or missing operations for the stated purpose.