NanoPDF

io.github.R09722akaBennettPublished by GitHub account R09722akaBennettv0.1.0Updated Oct 24, 2026

AI-powered PDF editing and generation MCP server using Gemini Pro.

VerifiedSTDIODesktop onlyFiles & StorageAI & ML

Overview

AI-generated overview

NanoPDF is a local MCP server that uses Gemini Pro to let an AI assistant edit and generate PDF documents.

What you can do
Edit existing PDF documents with AI assistance using Gemini Pro models from Google AI Studio, and generate new PDF files from prompts or content. The server runs locally over stdio and is intended for desktop use. No individual tools are documented in the supplied material, so specific operations are not listed.
When to use it
Useful when you want an assistant to produce or modify PDF files as part of a desktop workflow and you are comfortable sending document content to Google's Gemini API.
Requirements
Runs as a local process over stdio, distributed as a Docker image (docker.io/taibennett/nano-pdf-mcp:0.1.0), so Docker is needed. Requires a Google AI Studio API key supplied through the GEMINI_API_KEY environment variable. Desktop only; no web executable.
Before you install
Requires a Google AI Studio API key (GEMINI_API_KEY), which is a secret and may incur Gemini API usage costs. PDF content processed by the server is likely sent to Google's Gemini service, so avoid confidential documents unless that is acceptable. Editing and generating files writes data, so review outputs before relying on them.

Installation

In SourceWeft

  1. Open NanoPDF in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.