iLovePDF

@iLovePDF check my account info and tell me how many processing credits I have left this month

Your iLovePDF account is on the Premium plan with 450 processing credits remaining out of your 1,000 monthly allowance. Credits reset on the 15th of each month. Each compression or conversion operation typically consumes 1 credit per file, though batch operations may vary. You have sufficient capacity for moderate document processing through the end of your billing cycle.

This read-only check is useful before batch operations. The MCP returns credit balance and plan tier but does not forecast consumption — you'll need to estimate based on your workflow. No side effects; safe to run repeatedly.

@iLovePDF compress these three contract PDFs and return a ZIP so I can email them to the client without hitting attachment limits

Compressed 3 PDFs into a single ZIP archive (original total: 14.2 MB, compressed: 4.8 MB, 66% reduction). The output file is available as an offloaded download link valid for 2 hours. This operation consumed 3 processing credits. The temporary iLovePDF task has been cleaned up automatically.

This example shows a write operation with immediate cleanup. The MCP handles task lifecycle (create, upload, process, download, delete) in one call. Be aware: the download link expires quickly, and the operation is irreversible once credits are consumed.

@iLovePDF merge all the Q4 board meeting PDFs in chronological order and summarize the key decisions across the combined document

Merged 4 PDFs (October through December board minutes) into a single 47-page document. Scanning the combined file, the board approved three major decisions: (1) Q1 hiring freeze with exemptions for engineering, (2) pivot from enterprise to mid-market positioning, and (3)延delay of the Series B raise until Q2 metrics improve. The merger consumed 4 credits; the consolidated PDF is available for download.

This synthesis example pairs the MCP's merge capability with the AI's document reasoning. The merge happens first (consuming credits), then the AI reads the result. Useful for cross-document analysis, but note that large merges may hit rate limits on free-tier accounts.

When iLovePDF beats manual PDF wrangling for sales teams

A 3-person sales team closes deals by stitching case studies, pricing sheets, and signed NDAs into one proposal PDF—often minutes before a call. The merge and compress tools handle this in a single Switchy prompt: "merge proposal-draft.pdf, case-study-acme.pdf, and pricing-2024.pdf, then compress to under 5MB." The API key auth means no per-seat licensing hassle, and the 9-tool scope stays narrow enough that the AI won't hallucinate unrelated actions. The threshold: if your proposals need watermarking, redaction, or form-field editing, iLovePDF stops short and you'll want a heavier integration. For teams that just need fast merge-compress-convert cycles during live deal flow, this MCP closes the loop without leaving the workspace.

iLovePDF for high-volume ticket image cleanup

A 6-person support team receives 200+ tickets daily, many with oversized phone screenshots or multi-page scans that break email limits or slow the CRM. The compress-images and convert-images-to-PDF tools let agents prompt "compress all attachments in ticket #4891 and convert to PDF" without opening external tabs. The get-account-info tool surfaces remaining processing credits mid-shift, so the team knows when to throttle batch jobs. The trade-off: iLovePDF's compression is one-size-fits-all—no granular quality sliders—so if you need forensic-grade image fidelity or OCR output, you'll hit the ceiling fast. For teams prioritizing speed and attachment hygiene over pixel-perfect archives, iLovePDF keeps the ticket queue moving inside Switchy's shared context.

When iLovePDF's task cleanup matters for recurring workflows

A 2-person finance team builds a 40-slide board deck every month by converting Excel charts to images, merging department PDFs, and compressing the final file to under 10MB for secure email. The delete-task and get-task-status tools become critical here: after each monthly run, Switchy can confirm the iLovePDF worker cleaned up intermediate files, avoiding surprise storage or credit burn. The single API key covers both users without seat multiplication, and the 9-tool surface area means the AI rarely suggests irrelevant actions during the deck assembly prompt chain. The boundary: if your deck needs live Excel embedding or annotation layers, iLovePDF's convert-and-merge paradigm won't carry you. For teams running the same compress-merge-convert recipe monthly, this MCP turns a 15-minute manual ritual into a 2-minute prompted handoff.