io.scalably/dataforseo-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATAFORSEO_PASSWORD | Yes | DataForSEO account API password from the dashboard | |
| DATAFORSEO_USERNAME | Yes | DataForSEO account login (email) from the dashboard |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docs_indexB | Fetch the DataForSEO API documentation index (llms.txt), optionally filtered by section |
| docs_list_sectionsA | Return available DataForSEO API documentation section names |
| docs_searchA | Fetch DataForSEO API documentation from a documentation URL |
| api_requestB | Make an authenticated request to the DataForSEO API |
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 4 tools
The tools are mostly distinct: api_request handles API calls, docs_search fetches specific documentation pages, docs_index retrieves the documentation index, and docs_list_sections lists section names. However, docs_search and docs_index could be confused since both retrieve documentation-related content, though their purposes differ enough to avoid significant ambiguity.
Three tools share a consistent 'docs_' prefix with verb-noun style (docs_search, docs_index, docs_list_sections), but api_request breaks the pattern and uses a noun-noun construction. The naming is readable but not fully uniform, mixing conventions.
Four tools is an ideal size for a focused server that combines documentation retrieval with API request execution. Each tool has a clear purpose, and the count feels neither sparse nor bloated for the server's stated scope.
The tool set covers the full workflow: discovering available sections (docs_list_sections), browsing the index (docs_index), fetching specific documentation (docs_search), and making authenticated API requests (api_request). No obvious dead ends or missing core operations are apparent for a documentation and API helper server.