Build with MiOffice
Integrate file processing into your apps with our REST API, npm packages, MCP server, and browser extensions. PDF, image, video, and AI — all in one platform.
Quick Start
Node.js (npm)
// npm install mioffice-pdf-utils
const { compress } = require('mioffice-pdf-utils');
// Compress a PDF to under 5MB
const result = await compress({
input: './invoice.pdf',
maxSizeMB: 5,
quality: 'balanced'
});
console.log(result.outputPath); // ./invoice-compressed.pdf
console.log(result.reduction); // "72% smaller"REST API (cURL)
# Compress a PDF via RapidAPI
curl -X POST "https://miofficeai.p.rapidapi.com/pdf/compress" \
-H "X-RapidAPI-Key: YOUR_API_KEY" \
-H "X-RapidAPI-Host: miofficeai.p.rapidapi.com" \
-F "file=@invoice.pdf" \
-F "quality=balanced" \
-o compressed.pdfAPI Endpoints
/api/pdf-processCompress, merge, split, convert PDFs. Server-side Sharp + pdf-lib.
Compress PDF to target size, merge multiple files, extract pages
/api/image-processResize, compress, convert, crop images. Server-side Sharp.
Resize to 1024x768, compress JPEG to 80% quality, convert PNG to WebP
/api/video-processConvert, compress, extract audio from video. Server-side FFmpeg.
MOV to MP4, extract MP3, compress video, GIF to MP4
/api/ai-processAI-powered image processing. Server-side ONNX Runtime.
Remove background, upscale image, remove objects
/api/mcpModel Context Protocol server for AI assistants (Claude, ChatGPT).
Tool discovery, file processing via AI agents
Full endpoint documentation, request/response schemas, and rate limits available at docs.mioffice.ai.
Integrations & SDKs
npm Package
npmPDF utilities for Node.js — merge, split, compress, convert.
MCP Server
npmModel Context Protocol — let AI assistants use MiOffice tools.
GitHub Actions
GitHubCI/CD action for PDF processing in your build pipeline.
RapidAPI
RapidAPIManaged API hosting with usage-based pricing and API key auth.
Chrome Extension
ChromeAccess MiOffice tools from any tab. Right-click context menu integration.
VS Code Extension
VS CodeProcess files directly from your editor. PDF, image, and video tools.
Architecture: Client-First, Server-Fallback
MiOffice processes files client-side by default using WebAssembly (FFmpeg, ONNX Runtime, Tesseract). The server API exists as a fallback for first-time users before WASM binaries are cached, and for programmatic integrations where browser APIs aren't available.
Client (Browser)
WebAssembly + WebCodecs + Canvas. Zero uploads. GPU-accelerated.
Server (API)
Sharp + FFmpeg + ONNX. REST endpoints. RapidAPI-managed keys.
AI Agents (MCP)
Model Context Protocol server. Claude, ChatGPT, custom agents.
Common Use Cases
Document Pipelines
Compress PDFs in CI/CD, merge invoices, convert Word to PDF in batch.
Image Optimization
Resize product photos, convert to WebP, remove backgrounds for e-commerce.
Video Processing
Convert user-uploaded MOV/AVI to MP4, extract thumbnails, compress for streaming.
AI Assistants
Give your AI agent file processing abilities via MCP — no code required.