DataForSEO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | Yes | HTTP port — Railway injects this automatically | |
| LOG_LEVEL | No | debug/info/warn/error/silent | info |
| PUBLIC_URL | No | Public base URL, echoed on / | |
| TRUST_PROXY | No | Express trust proxy setting | 1 |
| MCP_AUTH_TOKEN | No | Comma-separated bearer tokens required on /mcp | |
| RATE_LIMIT_MAX | No | Maximum requests per rate limit window | 120 |
| MAX_BATCH_ITEMS | No | Max keywords/targets per batched call | 100 |
| DATAFORSEO_LOGIN | Yes | DataForSEO API login (server-side only) | |
| MAX_RESULT_ITEMS | No | Default rows per tool call | 50 |
| MCP_SESSION_MODE | No | stateless or stateful | stateless |
| DATAFORSEO_SANDBOX | No | Route everything to sandbox.dataforseo.com (free, dummy data) | false |
| MAX_RESPONSE_CHARS | No | Character budget per tool response | 100000 |
| DATAFORSEO_BASE_URL | No | Override; must be an https *.dataforseo.com host | https://api.dataforseo.com |
| DATAFORSEO_PASSWORD | Yes | DataForSEO API password (server-side only) | |
| MCP_ALLOWED_ORIGINS | No | Comma-separated allowed Origin values | |
| RATE_LIMIT_WINDOW_MS | No | Rate limit window | 60000 |
| DATAFORSEO_TIMEOUT_MS | No | Per-request timeout (max 180000) | 60000 |
| MAX_REQUEST_BODY_SIZE | No | JSON body limit on /mcp | 1mb |
| METADATA_CACHE_TTL_MS | No | Locations/languages cache TTL (6h) | 21600000 |
| DATAFORSEO_MAX_RETRIES | No | Retries for transient failures (never for task_post) | 2 |
| MAX_RESULT_ITEMS_HARD_CAP | No | Absolute row ceiling | 1000 |
| DATAFORSEO_MAX_CONCURRENCY | No | Max in-flight DataForSEO requests | 8 |
| MCP_SESSION_IDLE_TIMEOUT_MS | No | Stateful mode only: reap sessions idle this long | 1800000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/administrator-prog/data-for-seo'
If you have feedback or need assistance with the MCP directory API, please join our Discord server