Hosting

Vendor-hosted remote MCP

Transport

Streamable HTTP

Endpoint

https://api.scrapi.tech/mcp

Authentication

Hosted requests require a ScrAPI API key via X-API-KEY or apiKey query parameter; local package can read the key from environment.

Requirements

• ScrAPI account/API key
• For local Docker setup, Docker installed
• For local npx setup, Node.js/npm available
• MCP-compatible client

Setup steps

1. Get a ScrAPI API key from the vendor account portal.
2. For cloud Streamable HTTP, connect to https://api.scrapi.tech/mcp and set X-API-KEY to the key in the client's protected headers. SSE fallback is https://api.scrapi.tech/mcp/sse.
3. For local npm, configure command npx, args [-y, @deventerprisesoftware/scrapi-mcp], env SCRAPI_API_KEY=<key>.
4. For Docker, run docker with args run -i --rm -e SCRAPI_API_KEY deventerprisesoftware/scrapi-mcp and pass the key through environment config.
5. Reload client and verify using a permitted public URL and a read-only scrape.

Official ScrAPI MCP docs list exactly scrape_url_html and scrape_url_markdown; each accepts URL and optional browserCommands.

• scrape_url_html

  ScrAPI MCP Server: scrape url html.

  01
• scrape_url_markdown

  ScrAPI MCP Server: scrape url markdown.

  02

• Requires API credits for arbitrary sites. The publisher says new starter credits and training bonuses are no longer available (updated Oct. 6, 2026).

• official tool reference

  Official reference enumerates exactly scrape_url_html and scrape_url_markdown; both accept a URL and optional browserCommands.

• official documentation or source

  Official reference enumerates exactly scrape_url_html and scrape_url_markdown; both accept a URL and optional browserCommands.

Documentation checked 2026-10-28T12:55:35.000Z. Connection has not been runtime tested.