Apollo Proxy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APOLLO_API_URL | No | Override API endpoint | https://apolloai.team |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proxy_fetchA | Fetch any URL through Apollo's residential proxy network. Supports 190+ countries, rotating or sticky sessions, and handles anti-bot protection. Cost: $0.005/request (USDC on Base). Max response: 250KB. Rate limit: 100 req/min. |
| proxy_statusA | Check Apollo proxy service availability, pricing, and limits. Use this to verify the service is online before making requests. |
| list_countriesA | List available proxy exit countries. Apollo supports 190+ countries for residential proxy exits. Returns ISO 3166-1 alpha-2 country codes. |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: list_countries provides country options, proxy_fetch performs the core proxy request, and proxy_status checks service health and pricing. An agent can easily differentiate between them based on their descriptions.
All tool names follow a consistent verb_noun pattern (list_countries, proxy_fetch, proxy_status) with clear and descriptive naming. There are no deviations or mixed conventions, making the set predictable and readable.
With only 3 tools, the set feels thin for a proxy service domain, as it lacks operations like session management, configuration updates, or detailed analytics. However, it covers the absolute basics, placing it in the borderline range for appropriateness.
The tools cover core functions (listing, fetching, status) but have notable gaps, such as no ability to manage proxy sessions, set custom configurations, or retrieve usage metrics. This may cause agents to work around limitations, but the basics are present.