Evomi MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_urlA | Scrape a single URL. Modes: request (fast), browser (JS), auto (detect). Output: html, markdown, screenshot, pdf. Use ai_enhance with ai_prompt for AI extraction. |
| crawl_websiteA | Crawl a website to discover and scrape multiple pages. Follows links up to specified depth. The scraper_config can include a config_id to use saved settings, or full scraping options. |
| map_websiteB | Discover URLs from a website using sitemaps, CommonCrawl, or in-site crawling. |
| search_domainsA | Find domains by searching the web. Use this to discover websites when you don't know specific domains. Returns list of domains with URLs and titles. |
| agent_requestA | AI-powered conversational assistant that can do ANY Evomi operation. Ask it to: create configs, run scrapes, discover URLs, schedule jobs, check account info, and more. Examples: 'Scrape example.com and figure out what to extract', 'Create a config for Amazon products', 'Schedule my config to run daily', 'How many credits do I have?' |
| get_task_statusC | Check the status of an async task (scrape, crawl, or map). |
| get_account_infoA | Get account information including credit balance and user details. |
| list_configsC | List all saved scrape configurations. |
| create_configB | Create a new scrape configuration for reuse. |
| get_configA | Get a saved scrape configuration by ID. |
| update_configC | Update an existing scrape configuration. |
| delete_configB | Delete a scrape configuration. |
| generate_configC | Generate a scrape config from a natural language prompt using AI. |
| list_schemasC | List all saved extraction schemas. |
| create_schemaC | Create a new extraction schema for structured data extraction. |
| get_schemaA | Get a saved extraction schema by ID. |
| update_schemaC | Update an existing extraction schema. |
| delete_schemaC | Delete an extraction schema. |
| get_schema_statusC | Get the test status of an extraction schema. |
| list_storage_configsA | List all storage configurations (S3, GCS, Azure Blob). |
| create_storage_configC | Create a new storage configuration for saving scraped data. |
| update_storage_configC | Update an existing storage configuration. |
| delete_storage_configC | Delete a storage configuration. |
| list_schedulesC | List all scheduled scrape jobs. |
| create_scheduleC | Create a new scheduled scrape job that runs at regular intervals. |
| get_scheduleA | Get a scheduled job by ID. |
| update_scheduleC | Update an existing scheduled job. |
| delete_scheduleB | Delete a scheduled job. |
| toggle_scheduleA | Toggle a scheduled job active/inactive. |
| list_schedule_runsA | Get execution history for a scheduled job. |
| list_proxy_productsA | List the Evomi proxy products on this account with their gateway hostname, HTTP/SOCKS5 ports, remaining data balance, and proxy username. Products: rp = Premium Residential, rpc = Core Residential, dcp = Datacenter (Shared), mp = Mobile, static_residential = Static Residential. Returns NO proxy passwords — use get_proxy_credentials or build_proxy_connection_string for those. Call this first to see what the account actually has balance on. |
| get_proxy_credentialsA | Get the proxy username and PLAINTEXT PASSWORD for one Evomi proxy product, along with its gateway hostname, ports and remaining balance. Returns a live credential that grants paid proxy access — prefer build_proxy_connection_string when the user just wants something to paste into a client. Read-only: it does not rotate or change the password. SECRET HANDLING: the password is a live credential. Use it to carry out the task — write it into the config, command or code the user asked for — and do not repeat the value back in your reply. Show it only if the user explicitly asks to see it. |
| build_proxy_connection_stringA | Build ready-to-use Evomi proxy connection strings with geo targeting, sticky sessions and expert filters encoded into the password, plus a curl command to verify them. This is the tool to use when someone asks for 'a US residential proxy', 'proxies for Berlin', 'a sticky session', or how to configure a proxy in code. Fetches the account's own credentials, so the output CONTAINS THE PROXY PASSWORD. Validates the targeting against the chosen product and explains any unsupported combination instead of returning a string that would fail at connect time. Read-only. SECRET HANDLING: the password inside each connection string is a live credential. Use it to carry out the task — write it into the config, command or code the user asked for — and do not repeat the value back in your reply. Show it only if the user explicitly asks to see it. |
| generate_proxy_listA | Generate a bulk list of Evomi proxy strings server-side via the Public API (up to 50 per call), for pasting into tools that take a proxy list file. Output CONTAINS PROXY PASSWORDS. Supports only country/city/region/ISP targeting, sessions and ad blocking — for zip, ASN, pool mode or expert filters use build_proxy_connection_string instead. Fails if the product has no data balance. Read-only. SECRET HANDLING: the password inside each returned proxy line is a live credential. Use it to carry out the task — write it into the config, command or code the user asked for — and do not repeat the value back in your reply. Show it only if the user explicitly asks to see it. |
| get_proxy_usageA | Get bandwidth used for one Evomi proxy product over the last 24 hours, 3 days or 7 days, as a period total plus per-bucket figures — the same numbers as the dashboard usage chart. Use for 'how much traffic have I used', spend checks and usage trends. For how much balance is LEFT, use list_proxy_products instead. Returns no credentials. Read-only. |
| list_proxy_targeting_optionsA | Look up which countries, regions, cities, ISPs or continents can be targeted on a given Evomi proxy product, with an optional search filter. Call this before build_proxy_connection_string whenever a city, region or ISP is involved. Every entry gives an 'id' and a 'name': the 'id' is what the gateway accepts and what to pass back, the 'name' is the display form. The full catalogue is large, so results are filtered and capped. Returns no credentials. Read-only. |
| rotate_proxy_sessionA | MUTATING: force an existing Evomi sticky session onto a new exit IP. The current connection is dropped immediately and the old IP is released; the session id and credentials stay the same. Use when a session's IP has been blocked. Only call when the user asks to rotate or change IP — it disrupts anything currently using that session. Returns no credentials. |
| get_api_accessA | Check this account's access to Evomi's Scraper API and Scraping Browser: whether it is enabled, remaining credits, concurrency limit, max session length, and the endpoint URL to connect to. The per-service API keys are MASKED unless include_api_key is set to true. Use this to find out why a scrape failed for lack of credits, or to retrieve the scraper key needed to configure EVOMI_SCRAPER_API_KEY. Read-only. SECRET HANDLING: the API key returned when include_api_key is true is a live credential. Use it to carry out the task — write it into the config, command or code the user asked for — and do not repeat the value back in your reply. Show it only if the user explicitly asks to see it. |
| list_browser_profilesA | List the saved browser fingerprint profiles on this account (id, OS, browser, version, creation date). Use to find a profile id before launching a browser session. Does not return the fingerprint payload itself and returns no credentials. Read-only. |
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 39 tools
Most tools are organized by resource and have distinct purposes, but agent_request intentionally overlaps with every other operation by being able to 'do ANY Evomi operation'. The proxy credential/connection-string tools also overlap and rely heavily on detailed descriptions to avoid misselection.
The vast majority of tools follow a consistent verb_noun snake_case pattern: list_configs, create_schedule, get_proxy_credentials, rotate_proxy_session. The one clear outlier is agent_request, which is noun-like rather than an imperative verb, preventing a perfect score.
With 39 tools, the server is well past the 25-tool threshold for an agent-friendly surface. The count is inflated by multiple parallel CRUD families plus several proxy-related generators and builders, making tool selection harder even though the domains are related.
Core scraping and proxy lifecycle coverage is strong: scrape/crawl/map, configs, schemas, schedules, proxies, and account info are all represented. However, storage configs lack a get_storage_config, browser profiles only have a list operation, and async tasks have no cancellation or history listing, so some workflows dead-end.