Cofferdock

com.cofferdockPublished by cofferdock.comOfficial publisherv1.0.1Updated Oct 26, 2026

Real files for AI assistants: HTML to image/PDF, screenshots, QR, charts, PDF tools, validators.

VerifiedStreamable HTTPWeb executableFiles & StorageMedia & Design

Overview

AI-generated overview

Remote Cofferdock server that lets an assistant turn HTML into images or PDFs and produce screenshots, QR codes, charts, PDF tools and validators.

What you can do
  • Render HTML into images or PDF files
  • Capture screenshots
  • Generate QR codes and charts
  • Run PDF tools
  • Run validators on generated or supplied content
When to use it
Useful when an assistant needs to hand back real files rather than text: rendered HTML, screenshots, QR codes, charts or PDFs, and when you want that rendering done by a hosted service instead of a local toolchain.
Requirements
A remote endpoint at api.cofferdock.com over streamable HTTP. Authentication is required: either OAuth sign-in with a Cofferdock account (Claude, ChatGPT and similar clients) or an x-api-key header with a Cofferdock API key, which the manifest describes as optional and free to register.
Before you install
The server requires authentication, so an account or an API key in the x-api-key header is involved; treat that key as a secret. Content sent for rendering, such as HTML, is processed by a third-party hosted service. No tool list was provided, so the exact write or file-return behaviour could not be verified.

Installation

In SourceWeft

  1. Open Cofferdock 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.cofferdock%2Fcofferdock/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": {
    "cofferdock": {
      "type": "http",
      "url": "https://api.cofferdock.com/mcp"
    }
  }
}

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.1LatestSep 26, 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.