MCP server for using ScrAPI to scrape web pages.
MCP server for using ScrAPI to scrape web pages. That is what the scrapi mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
ScrAPI MCP Server lets MCP-compatible clients scrape web pages through ScrAPI.
The server publishes 13 tools. What each one is for:
Long — running pages, CAPTCHA flows, and heavy JavaScript pages can take several minutesClick — {"click": "#buttonId"}Input — {"input": {"input[name='email']": "value"}}Select — {"select": {"select[name='country']": "USA"}}Scroll — {"scroll": 1000}Wait — {"wait": 5000}WaitFor — {"waitfor": "#elementId"}JavaScript — {"javascript": "console.log('test')"}scrape_url_html — Use this when you need the page structure, links, tables, embedded metadata, or custom downstream parsingscrape_url_markdown — Use this when the text content matters more than the HTML structure, for example article extraction, product copy, search result summaries, orCursor — Cursor supports project configuration at .cursor/mcp.json and global configuration at ~/.cursor/mcp.json. See the [Cursor MCPWindsurf — Windsurf Cascade stores MCP servers in ~/.codeium/windsurf/mcp_config.json. You can also add servers from Windsurf Settings > Cascade > MCP ServersBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: SCRAPI_API_KEY, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Choose one of the following runtime options: - Node.js 18 or newer for npx or local development. - Docker for container-based usage. - An MCP-compatible client such as Claude Desktop, MCP Inspector, or another client that supports stdio or Streamable HTTP MCP servers.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Scrapi MCP's toolset — Long, Click, Input and 10 more — is a fair guide to whether it matches your workflow. It is maintained by DevEnterpriseSoftware; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Long | running pages, CAPTCHA flows, and heavy JavaScript pages can take several minutes. |
| Click | {"click": "#buttonId"} |
| Input | {"input": {"input[name='email']": "value"}} |
| Select | {"select": {"select[name='country']": "USA"}} |
| Scroll | {"scroll": 1000} |
| Wait | {"wait": 5000} |
| WaitFor | {"waitfor": "#elementId"} |
| JavaScript | {"javascript": "console.log('test')"} |
| scrape_url_html | Use this when you need the page structure, links, tables, embedded metadata, or custom downstream parsing. |
| scrape_url_markdown | Use this when the text content matters more than the HTML structure, for example article extraction, product copy, search result summaries, or LLM-friendly page analysis. |
| Cursor | Cursor supports project configuration at .cursor/mcp.json and global configuration at ~/.cursor/mcp.json. See the [Cursor MCP documentation](https://docs.cursor.com/context/model-context-protocol). |
| Windsurf | Windsurf Cascade stores MCP servers in ~/.codeium/windsurf/mcp_config.json. You can also add servers from Windsurf Settings > Cascade > MCP Servers. See the [Windsurf MCP documentation](https://docs.windsurf.com/windsurf |
| Codex | Codex supports MCP servers in the CLI and IDE extension. Both use the same MCP configuration. By default, Codex stores it in ~/.codex/config.toml; trusted projects can also use .codex/config.toml. See the [Codex MCP docu |
### Claude Desktop with Docker
```json
{
"mcpServers": {
"ScrAPI": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SCRAPI_API_KEY",
"deventerprisesoftware/scrapi-mcp"
],
"env": {
"SCRAPI_API_KEY": "your-scrapi-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
Choose one of the following runtime options: - Node.js 18 or newer for npx or local development. - Docker for container-based usage. - An MCP-compatible client such as Claude Desktop, MCP Inspector, or another client that supports stdio or Streamable HTTP MCP servers.
| Variable | Description | Required |
|---|---|---|
| SCRAPI_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.