Skip to main content
Glama
dhanavathsrikanth

screenshotapi-mcp

by dhanavathsrikanth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to screenshotapi-mcp

No user-submitted related servers found.

    Related Servers

    • Screenshot API

      raphy78626
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to capture any public URL as PNG, JPEG, or PDF via REST API or MCP tools, including screenshot capture, page description, and PDF rendering.
      13 npm
      MIT

    • bigapi

      BiGapi-2026
      A
      license
      A
      quality
      A
      maintenance
      Deterministic file operations for AI agents: 40 operations over plain HTTPS. PDF merge, split, redact, sanitize, OCR, Office and PDF to Markdown, RAG chunking, charts, QR codes, C2PA AI labelling. find_tool suggests the right one. $0.01 per operation, 100 free, no signup, credits never expire.
      2
      5
      600 npm
      MIT
    • @crawlbrulee/mcp by crawlbrulee

      @crawlbrulee/mcpofficial

      crawlbrulee
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP-aware AI agents to scrape web pages into markdown, screenshots, metadata, and links, map sites, run asynchronous scrape jobs, and check usage, with EU-hosted, GDPR-aligned processing.
      7
      650 npm
      Apache 2.0

    • Latchshot for Gemini CLI

      BaiqingL
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides two MCP tools (capture_page and get_usage) that let Gemini CLI capture public web pages as PNG/JPEG/PDF and check render quota, all via a hosted Streamable HTTP endpoint without local browser.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tools are mostly distinct: render-screenshot captures full pages, capture-element targets specific DOM elements, convert-to-markdown extracts text, get-screenshot retrieves by ID, and get-usage is account-related. The only minor overlap is between the two capture tools, but their descriptions clearly differentiate full-page vs. element capture.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun pattern with hyphenated lowercase (render-screenshot, capture-element, convert-to-markdown, get-usage, get-screenshot). The verbs clearly indicate actions, and the nouns identify the object, making the naming predictable and easy to infer.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a screenshot utility. Each tool serves a distinct purpose without redundancy, covering the core capture, retrieval, conversion, and account management needs. This count is appropriate and not overwhelming or thin.

    Completeness4/5

    The tool surface covers the primary workflow: capturing screenshots (full-page and element), converting to markdown, retrieving past captures, and checking usage. Minor gaps exist, such as no tool for listing all captures or deleting them, but these are not essential for the core screenshot API functionality and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources