MochiPDF

io.github.cbolgianoPublished by GitHub account cbolgianov3.1.0Updated Oct 24, 2026

Remote MCP server for HTML-to-PDF and screenshots with OAuth and API-key auth.

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

MochiPDF is a remote MCP server that lets an assistant convert HTML to PDF and capture screenshots, with OAuth or API-key authentication.

What you can do
Convert HTML content into PDF documents through the remote service. Capture screenshots of rendered pages or content. Authenticate requests with OAuth or an API key supplied in the X-API-Key header.
When to use it
Useful when an assistant needs to turn HTML into a PDF file or take screenshots without running a local rendering toolchain, and you are comfortable sending that content to a hosted service.
Requirements
A remote MCP endpoint at mochipdf.com over streamable HTTP. Authentication is required: OAuth, or an API key passed in the X-API-Key header. Network access to the service is needed.
Before you install
The service requires an API key or OAuth credentials; keep the X-API-Key value private. HTML content submitted for conversion or screenshot is sent to a third-party hosted service, so avoid sending sensitive or confidential material unless that is acceptable.

Installation

In SourceWeft

  1. Open MochiPDF 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/io.github.cbolgiano%2Fmochipdf/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": {
    "mochipdf": {
      "type": "http",
      "url": "https://mochipdf.com/mcp"
    }
  }
}

README

This repository has no README.

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. v3.1.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.