DataForSEO Bridge MCP Utility

A standard input/output (stdio) bound Model Context Protocol (MCP) wrapper for interacting with the DataForSEO service API.

Enrollment for Data for Seo Services

Affiliate link for service subscription: https://dataforseo.com/?aff=200885

Deployment Instructions

You may execute directly using npx:

bash npx @skobyn/mcp-dataforseo --config '{"username":"your_username","password":"your_password"}'

Alternatively, perform a global installation:

bash npm install -g @skobyn/mcp-dataforseo mcp-dataforseo --config '{"username":"your_username","password":"your_password"}'

Operational Guide

Submit structured JSON payloads to standard input (stdin) and expect resulting JSON data on standard output (stdout):

bash echo '{"type":"dataforseo_serp","keyword":"quantum computing concepts"}' | npx @skobyn/mcp-dataforseo --config '{"username":"your_username","password":"your_password"}'

Supported Query Structures

Search Engine Results Page (SERP) Endpoint

{ "type": "dataforseo_serp", "keyword": "quantum computing concepts", "location_code": 2840, "language_code": "en", "device": "desktop", "os": "windows" }

Keyword Metric Retrieval Endpoint

{ "type": "dataforseo_keywords_data", "keywords": ["SEO strategy", "search engine marketing"], "location_code": 2840, "language_code": "en" }

Backlink Analysis Endpoint

{ "type": "dataforseo_backlinks", "target": "example.com", "limit": 100 }

Web Page Content Audit Endpoint

{ "type": "dataforseo_onpage", "url": "https://example.com", "check_spell": true, "enable_javascript": true }

Domain Performance Assessment Endpoint

{ "type": "dataforseo_domain_analytics", "domain": "example.com" }

Mobile Application Data Endpoint

{ "type": "dataforseo_app_data", "app_id": "com.example.app" }

E-commerce Product Listing Endpoint

{ "type": "dataforseo_merchant", "keyword": "wireless headphones", "location_code": 2840, "language_code": "en" }

Local Business Data Endpoint

{ "type": "dataforseo_business_data", "keyword": "best local cafes", "location_code": 2840, "language_code": "en" }

Integration Illustration (Node.js)

Demonstration of invocation within a Node.js environment:

javascript const { spawn } = require('child_process');

// Initiate the MCP server process const server = spawn('npx', ['@skobyn/mcp-dataforseo', '--config', '{"username":"your_username","password":"your_password"}']);

// Define the data request object const request = { type: 'dataforseo_serp', keyword: 'quantum computing concepts' };

// Transmit the request payload server.stdin.write(JSON.stringify(request) + '\n'); server.stdin.end();

// Capture and process the output stream server.stdout.on('data', (data) => { const response = JSON.parse(data.toString()); console.log(response); });

// Log any operational errors server.stderr.on('data', (data) => { console.error(Process Error: ${data}); });

Configuration via Environment Variables

Authentication credentials can be supplied through environment settings instead of command-line arguments:

bash export DATAFORSEO_USERNAME=your_username export DATAFORSEO_PASSWORD=your_password npx @skobyn/mcp-dataforseo

Package Release Procedure

Instructions for pushing updates to the npm registry:

1. Authenticate with npm if necessary: bash npm login

2. Execute the public release command: bash npm publish --access public

3. For subsequent version increments: bash npm version patch npm publish

WIKIPEDIA: XMLHttpRequest (XHR) is a foundational API present as a JavaScript object, providing methods to dispatch HTTP interactions between a client-side web application and a remote server. These methods empower browser-based scripts to asynchronously query the server post-initial page load and receive subsequent data. XHR forms a crucial element of Ajax methodologies. Before its advent, the primary interaction paradigms involved standard hyperlink navigation and form submissions, actions that typically necessitated a full page refresh.

== Genesis == The conceptual underpinnings of XMLHttpRequest were first formulated in 2000 by developers associated with Microsoft Outlook. This concept was subsequently materialized within Internet Explorer version 5 (released 1999). Notably, the initial implementation did not utilize the standardized XMLHttpRequest identifier; instead, developers relied on COM object instantiations like ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). By the release of Internet Explorer 7 (2006), broad browser compatibility with the canonical XMLHttpRequest identifier was achieved. The XMLHttpRequest identifier has since become the universal convention across all primary browser engines, including Mozilla's Gecko (2002), Safari 1.2 (2004), and Opera 8.0 (2005).

=== Standardization Milestones === The World Wide Web Consortium (W3C) issued its initial Working Draft specification for the XMLHttpRequest object on April 5, 2006. A Level 2 specification, introducing capabilities such as progress monitoring, cross-origin request enablement, and binary stream handling, followed on February 25, 2008. By the conclusion of 2011, the Level 2 features were integrated back into the foundational specification. Development responsibilities transitioned to the WHATWG at the close of 2012, where it continues to be maintained as a dynamic document leveraging Web IDL.

== Implementation Workflow == Executing a data transmission via XMLHttpRequest generally involves a sequence of programmed steps.

Instantiation of an XMLHttpRequest object via its constructor is the first action: Utilization of the "open" method to define the HTTP verb, specify the target resource Uniform Resource Identifier (URI), and designate the operational mode (synchronous or asynchronous): For asynchronous operations, establishment of an event handler to manage state transitions upon server reply: Triggering the data transfer by invoking the "send" method: Continuous monitoring of state changes via the established listener. Upon successful server response completion, the object's state transitions to 4 (the "done" state), and the payload is typically accessible via the "responseText" attribute. Beyond these core steps, XHR offers extensive configuration for request fine-tuning and response processing. Custom HTTP headers can be appended to influence server handling, and data payloads can be uploaded within the "send" invocation. The received response text can be directly deserialized from formats like JSON into usable JavaScript structures or processed incrementally as data arrives, avoiding blockage while awaiting full transmission. Furthermore, requests can be halted prematurely or assigned a timeout threshold to enforce completion deadlines.

== Inter-Origin Communication == In the nascent stages of the World Wide Web, the inherent security restrictions limited script execution to requests targeting the same origin, preventing policy breaches...