Scrape websites to markdown
Scrape websites to markdown. The usescraper mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
This is a TypeScript-based MCP server that provides web scraping capabilities using the UseScraper API. It exposes a single tool 'scrape' that can extract content from web pages in various formats.
Everything the assistant can do here goes through one of these:
scrape — Extract content from a webpageParameters — - url (required): The URL of the webpage to scrapeTools — The Tools tool exposed by this serverDebugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCPInstallation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need one environment variable: USESCRAPER_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Usescraper's toolset — scrape, Parameters, Tools and 1 more — is a fair guide to whether it matches your workflow. It is maintained by tanevanwifferen; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Usescraper's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| scrape | Extract content from a webpage |
| Parameters | - url (required): The URL of the webpage to scrape |
| Tools | The Tools tool exposed by this server. |
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script: |
{
"mcpServers": {
"usescraper": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"USESCRAPER_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| USESCRAPER_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.