Skip to main content
Glama
screenshotfreeapi

screenshotfreeapi

screenshotfreeapi-mcp

MCP server for ScreenshotFreeAPI — capture websites, render HTML/PDF, and fetch app store listing screenshots from any MCP-compatible AI client (Claude Desktop, Cursor, VS Code Copilot, Cline, Windsurf, etc.).

Setup

Get an API key from your ScreenshotFreeAPI dashboard, then add this server to your MCP client's config.

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "screenshotfreeapi": {
      "command": "npx",
      "args": ["-y", "screenshotfreeapi-mcp"],
      "env": {
        "SCREENSHOTFREEAPI_KEY": "sfa_your_api_key_here"
      }
    }
  }
}

Other MCP clients (Cursor, Cline, Windsurf) use the same command/args/env shape in their own config file — consult your client's docs for the config file location.

Related MCP server: PuppeteerMCP Server

Environment variables

Variable

Required

Description

SCREENSHOTFREEAPI_KEY

Yes

Your API key (sfa_...). Without it, every tool call fails with 401.

SCREENSHOTFREEAPI_BASE_URL

No

Override the API base URL. Defaults to https://api.screenshotfreeapi.com.

Tools

Tool

Description

screenshot_web

Capture a website screenshot (PNG/JPEG/WebP/PDF), with AI element targeting, full-page, custom viewport, and ad-block options.

screenshot_mobile

Capture app store listing screenshots (iOS/Android) by app name or bundle ID.

render_html

Render raw HTML/CSS to an image or PDF.

get_job_status

Poll the status of a screenshot job.

get_job_result

Fetch the result (URLs + metadata) of a completed job.

list_jobs

List recent jobs for the authenticated account.

check_quota

Check remaining screenshot quota and current plan.

All capture tools are asynchronous: they enqueue a job and return a jobId. Use get_job_status to poll, then get_job_result once status is completed.

Local development

npm install
npm run dev        # run directly with tsx
npm run build       # compile to dist/ for npx/publish
npm run typecheck

License

MIT

Available Tools

7 tools
check_quotaA

Check the remaining screenshot quota and current plan for the authenticated API key.

Inputs: no named parameters.

get_job_resultA

Retrieve the screenshot URLs and metadata for a completed job. Returns presigned URLs (15-minute TTL). Returns an error if the job is still in progress.

Inputs: jobId (required).

get_job_statusA

Poll the current status and progress of a screenshot job. Status values: queued → processing → completed | failed.

Inputs: jobId (required).

list_jobsA

List recent screenshot jobs for the authenticated API key. Filter by status or type.

Inputs: status, type, limit.

render_htmlA

Render a raw HTML string (email template, certificate, report card, etc.) to a screenshot image. Requires STARTER plan.

Inputs: html (required), css, format, dimensions, +1 more.

screenshot_mobileA

Fetch app store listing screenshots for any iOS or Android app by name or bundle/package ID. Returns screenshots from Google Play and/or the Apple App Store along with rich metadata (version, rating, reviews, category).

Inputs: appName, bundleId, platform, waitForResult.

screenshot_webA

Capture a screenshot of any public website URL. Supports AI-targeted sections, full-page capture, PDF export, and custom viewport dimensions. Returns a presigned URL to the screenshot image.

Inputs: url (required), description, element, format, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the screenshot service: quota checking, job management (listing, status, results), and three distinct screenshot sources (web, mobile, HTML). No two tools have overlapping functionality.

    Naming Consistency4/5

    Tool names generally follow a verb_noun pattern (check_quota, get_job_result, get_job_status, list_jobs, render_html), but screenshot_mobile and screenshot_web use a noun-verb style. This minor inconsistency reduces the score slightly.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose: it covers screenshot generation from multiple sources, job tracking, and quota checking without unnecessary clutter.

    Completeness4/5

    The tool surface covers the core screenshot workflow (create, track, retrieve) and multiple input types. Minor gaps include no way to cancel/delete jobs or manage API keys, but these are not critical for basic usage.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      An MCP server that enables capturing website screenshots with full-page, element-specific, and device-responsive capabilities through natural language commands.
      3
      21 npm
      62
      MIT