Web to Text (Apify) by Dataset Works

dev.datasetworksPublished by datasetworks.devv1.0.0Updated Nov 17, 2026

Turn web pages into clean Markdown text for LLMs and RAG. Respects robots.txt.

The publisher's own server: Apify MCP Server

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote Apify-hosted MCP server that turns web pages into clean Markdown text for LLMs and RAG pipelines.

What you can do
  • Convert web pages into clean Markdown text suitable for LLMs and RAG.
  • Respect robots.txt when fetching pages.
  • Connect through Apify's hosted MCP endpoint, signing in with OAuth or an Apify API token.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when an assistant needs readable page text for summarization, retrieval or knowledge-base building, and you would rather use a hosted Apify endpoint than run a local scraper.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: either OAuth sign-in to Apify or an Apify API token supplied in the Authorization header as a Bearer token. Network access to the endpoint is needed.
Before you install
The Authorization header carries an Apify API token, which is a credential; keep it secret and prefer OAuth where possible. Page content is fetched through Apify's hosted service, so the URLs you submit are visible to that third party. Apify usage may be subject to account plans or billing.

Installation

In SourceWeft

  1. Open Web to Text (Apify) by Dataset Works in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.datasetworks%2Fweb-to-text/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "web-to-text-apify-by-dataset-works": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=datasetworks/web-to-text"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 17, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Apify integrations