MCP server for web scraping Use domscout as agent tools
The @domscout/mcp package exposes this API as MCP tools, so an agent platform can read pages, capture images, extract structured data, and run bounded crawls without you writing an HTTP client. Every tool is the same route documented in the API guide, with the same plan gates, the same credit weights, and the same safety controls.
01 · Install
Add it to your client
Hosted: nothing to install
A client that accepts a remote server URL can use https://www.domscout.io/mcp directly. If it supports OAuth, it asks you to sign in to domscout and needs no key; otherwise send your key as Authorization: Bearer ds_.... The tools and the credits are the same as the package's.
Or run the package yourself: create a key in the dashboard, then pick your client below. The package runs through npx, so there is nothing to install and nothing to update - you need Node.js 20 or newer.
Claude Code
Cursor and VS Code
Both buttons hand your editor the configuration below with a placeholder key. Replace ds_your_key_here with your own before the first call.
Claude Desktop, Windsurf, and any other MCP client
Paste this into the client's configuration file. The parts that matter in any format are the command (npx -y @domscout/mcp) and the DOMSCOUT_API_KEY environment variable.
The default target is https://api.domscout.io.
02 · Tools
What the agent can call
Costs come back with the result
No request exceeds 10 credits, and every tool result carries what it cost and what remains, so an agent can budget without a second call.
Plan gates still apply
A tool is usable when its plan and the deployment state allow the underlying route. Trusted browser-side JavaScript has a separate account entitlement. domscout_check_credits reports which capabilities this key can actually use.
Web search is not among them. POST /search is withheld while no provider is configured, so no MCP tool wraps it.
03 · Resources
Documentation the agent can read directly
04 · Keys
Where the key lives
The server sends an x-api-key to the API host and reads the response. It holds no browser, database, or billing credential. The hosted endpoint, when you sign in with OAuth, holds no key of yours at all: it calls the API as your account. Keep the key in your MCP client's environment block - never commit it, and never paste it into a prompt, because prompt text is frequently logged by the platform running the agent.