Website Screenshot & PDF API

com.tidewellsoftwarePublished by tidewellsoftware.comv1.0.0Updated Nov 11, 2026

Full-page screenshots and URL to PDF in real Chrome, via the Apify actor

The publisher's own server: screenshot.com.ar

VerifiedStreamable HTTPWeb executableBrowser Automation

Overview

AI-generated overview

Apify-hosted MCP server that lets an assistant capture full-page screenshots and convert URLs to PDF using real Chrome.

What you can do
  • Capture full-page screenshots of a web page in real Chrome
  • Convert a URL into a PDF document
  • Run these captures through the Apify actor for website screenshots and PDFs
When to use it
Useful when you need a rendered visual snapshot or a PDF copy of a specific web page, for example for reports, documentation, or archiving a page as it looks in a real browser.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. Authentication is required: an Apify API token supplied in the Authorization header, or OAuth in clients that support it. An Apify account is implied by the token.
Before you install
The Authorization header carries an Apify API token, so treat it as a secret. Captures run on Apify's infrastructure, so the URLs you submit are sent to that third party, and Apify usage may be billed to your account.

Installation

In SourceWeft

  1. Open Website Screenshot & PDF API 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/com.tidewellsoftware%2Fwebsite-screenshot-pdf/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": {
    "website-screenshot-pdf-api": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=tidewell/website-screenshot-pdf"
    }
  }
}

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 11, 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 Screenshot integrations