Blinkpdf

io.blinkpdfPublished by blinkpdf.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Render Markdown and LLM output into accessible PDF/UA-1 PDFs. No headless Chromium.

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

A remote MCP server that renders Markdown and LLM output into accessible PDF/UA-1 PDF documents without a headless browser.

What you can do
Convert Markdown or LLM-generated text into PDF documents, producing accessible PDF/UA-1 output. Rendering is handled by the hosted service rather than a headless Chromium instance. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to turn Markdown or model output into a shareable, accessibility-compliant PDF, and you prefer a hosted service over running a local rendering toolchain.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's address. OAuth authentication is required. No environment variables or headers are declared.
Before you install
You must authorize the service through OAuth, and any Markdown or LLM output sent for rendering goes to the third-party provider. Review what content you submit before converting it.

Installation

In SourceWeft

  1. Open Blinkpdf 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.blinkpdf%2Fblinkpdf/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": {
    "blinkpdf": {
      "type": "http",
      "url": "https://mcp.blinkpdf.io/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.0LatestSep 16, 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.