Skip to main content
Glama
beznazwiska

@codetoimage/mcp-server

by beznazwiska

Related Servers

Alternatives to @codetoimage/mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Screenshot and HTML Rendering MCP Server for AI Agents. Capture screenshots, render HTML to images, and generate PDFs via simple API calls. Compatible with Claude, Cursor, and any MCP client.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to render any URL or raw HTML into PDF files or PNG/JPEG/WebP screenshots over MCP stdio or Streamable HTTP. Output stays in memory with SSRF protection, bounded concurrency, and configurable size and timeout limits.
      10 npm
      1
      MIT
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for the SnapAPI web capture API. Take screenshots, scrape pages, extract structured data, generate PDFs, record videos, and run AI analysis on any URL — all from Claude, Cursor, VS Code, or any MCP client. 9 tools, 30+ device presets, ad/cookie blocking. Install: npx snapapi-mcp
      9
      3 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to navigate, screenshot, read console/network, and crawl links in HTML documentation via a co-located headless Chromium and VSCode webview pane.
      24 npm
      -

    TDQS

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one returns inline image data, the other a temporary URL. Their descriptions explicitly contrast when to use each, leaving no ambiguity.

    Naming Consistency5/5

    Both tool names follow the exact pattern 'render_html_to_X', where X is the output type (image vs url). The naming is perfectly consistent and descriptive.

    Tool Count5/5

    With only two tools, the server is tightly scoped to its single purpose of rendering HTML to images. Each tool covers a necessary output format, so the count is ideal.

    Completeness5/5

    For a server focused solely on rendering HTML to images, offering both inline and URL outputs covers all common use cases. There are no missing features or dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues