URL to Markdown — Clean Page Text, Selectors & Source Links

io.github.kriton-devPublished by GitHub account kriton-devv1.0.24Updated Nov 17, 2026

Turn public web pages into clean Markdown for LLMs, RAG and AI agents

The publisher's own server: Source

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Remote Apify-hosted MCP server that turns public web pages into clean Markdown for LLMs, RAG pipelines and AI agents.

What you can do
  • Convert public web pages into clean Markdown text suitable for LLM prompts and RAG ingestion
  • Extract page content using selectors and keep source links with the output
  • Deliver results through a hosted Apify endpoint rather than a local process
When to use it
Useful when an assistant needs readable page text for summarization, retrieval or agent workflows, and you would rather call a hosted Apify Actor than run your own scraper.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: either an Apify API token sent as a Bearer value in the Authorization header, or OAuth sign-in to Apify. Runs are billed to your Apify account.
Before you install
Runs are billed to your Apify account at the Actor's pay-per-event prices, so usage costs money. The Authorization header carries an Apify API token, which is a secret. Page content is fetched through Apify's hosted service, so the URLs you submit are visible to that third party.

Installation

In SourceWeft

  1. Open URL to Markdown — Clean Page Text, Selectors & Source Links 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/io.github.kriton-dev%2Furl-to-markdown/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": {
    "url-to-markdown-clean-page-text-selector": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=hermeskd/url-to-markdown"
    }
  }
}

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.24LatestNov 17, 2026

Score

67% 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
  • 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 Source integrations