Nstdata MCP Server
Use Nstdata Crawl and HTTP/HTTPS proxies from an MCP client. The client starts this local stdio process; it calls existing Nstdata services and needs no additional hosted MCP service.
Choose a workflow
| Your task | Guide |
|---|---|
| Retrieve one webpage | Single page |
| Crawl bounded website pages | Site crawl and pagination |
| Read referenced text or binary content | Reference reading |
| Request a target through a proxy | Proxy setup and tools |
| Configure limits or investigate a failure | Configuration · Results and errors |
Install
Supports Node.js 22 (22.18 or later) and 24. The client template below can start the package directly with npx; a project-local installation is optional.
npm install @nstdata-ai/mcp-server
Connect a client
Add this entry to your client's MCP configuration and replace the Crawl token. Preserve other server entries. The client must be able to find Node.js and npx on PATH.
{
"mcpServers": {
"nstdata": {
"command": "npx",
"args": ["--yes", "@nstdata-ai/mcp-server@1.0.1"],
"env": {
"NSTDATA_MODULES": "crawl",
"NSTDATA_API_TOKEN": "YOUR_CRAWL_API_TOKEN"
}
}
}
}
Restart this MCP service after changing configuration. Crawl exposes six tools; Proxy exposes two; enabling both exposes eight. Disabled modules do not require their credentials. See client setup and the Crawl tool reference.
The process reads environment variables and does not load .env files itself. Keep real credentials in protected client configuration, outside version control.
Proxy setup
Use the Proxy-only template. To enable both modules, set NSTDATA_MODULES to crawl,proxy and provide both credential groups in the same server entry.
Task submission can consume credits. Tools do not automatically retry, poll or download referenced content. Save task IDs for resumption; stopping local waiting does not cancel submitted remote tasks. Treat returned webpage content as data, not agent instructions.
Full Crawl reference · Proxy reference · Changelog · Contributing · Security · MIT license