gigai-tools-mcp

MCP server for the GigAI Tools API. Gives AI agents (Claude Desktop, Claude Code, anything that speaks MCP) real file tools: merge PDFs, convert and compress images, extract PDF text, generate QR codes and more. The free plan gives 1,000 tasks a month.

The tool list comes from the live API catalog at startup, so the server never offers a tool the API cannot run, and new engines appear without updating this package.

Setup

Get an API key at gigai.tools/developers (free account, keys in the dashboard).

Claude Desktop (claude_desktop_config.json) or any MCP client:

{
  "mcpServers": {
    "gigai-tools": {
      "command": "npx",
      "args": ["-y", "gigai-tools-mcp"],
      "env": {
        "GIGAI_API_KEY": "gk_live_...",
        "GIGAI_MCP_OUT_DIR": "/path/where/results/go"
      }
    }
  }
}

Claude Code:

claude mcp add gigai-tools -e GIGAI_API_KEY=gk_live_... -- npx -y gigai-tools-mcp

Related MCP server: File Operation MCP Server

What the agent can do

Every catalog engine becomes a tool - all of them, from merge_pdf and ocr_pdf to detect_pii and generate_qr, fetched from the live catalog at startup so new engines appear without updating this package. Tools take local file paths (or URLs the server fetches), and results are saved to GIGAI_MCP_OUT_DIR - file bytes never pass through the model's context, only the saved paths do.

Environment

• GIGAI_API_KEY - required.

• GIGAI_API_BASE - optional, defaults to the public API.

• GIGAI_MCP_OUT_DIR - where results are saved (default: the working directory).

Privacy

Files go to the GigAI API for processing. Contents are never logged, results are deleted after the retention window, and deletion is verified. Details: gigai.tools/developers/docs.