FlipLink CLI vs API vs MCP: Which Integration Should You Use?

FlipLink gives you three ways to automate flipbooks without touching the dashboard: a command-line tool, a REST API, and an MCP server for AI assistants. They sound like three different products, but they aren't. They're three front doors to the same engine — the same endpoints, the same data, the same account.

So the real question isn't “which is best?” It's “which fits what you're doing right now?” This guide gives you a neutral comparison and a quick “pick one” rule.

Three front doors, one API

Everything FlipLink can do programmatically runs through one REST API at https://go.fliplink.me, authenticated with an X-Api-Key header. The CLI and the MCP server are both built directly on top of that same API — in fact the CLI command list and the MCP tool list are generated from the same endpoint spec, so they can't drift out of sync.

That has a useful consequence: whatever you can do in one, you can do in all three. The differences are about who is driving and how much code you want to write — not about capability.

Decision matrix

All three share the same response model: every reply is JSON with a top-level Result of "OK" or "ERROR", and the same rate limit of 300 requests per minute per key.

When to reach for each one

CLI — for scripts, terminals, and CI/CD

Use the CLI when you live in a terminal or a pipeline. It's the fastest path from “I have a PDF” to “I have a published flipbook” without writing an HTTP client. Wrap it in a shell script, a cron job, or a GitHub Actions step and you have repeatable automation. Add --json to any command and pipe it to jq for scripting. See getting started with the CLI.

API — for applications

Use the API when FlipLink is a feature inside something you're building — a customer portal that generates flipbooks on signup, a dashboard that pulls lead capture data, or a CRM sync. You get full control and can call it from any language that speaks HTTP. The API reference has every endpoint with a live Try-It console.

MCP — for AI assistants and non-developers

Use the MCP server when the person (or agent) doing the work shouldn't have to know an endpoint exists. Connect FlipLink to Claude, Cursor, or another MCP client and you can say “publish the Q3 deck and give me the share link” in plain language. The assistant picks the right tool and fills in the parameters. It's the lowest-friction option for non-coders — and it ships with safety guardrails so destructive actions need confirmation first.

🚀

Try FlipLink Free

Convert your PDF in seconds. No sign-up, no credit card — just upload and go.

Drop your PDF here or click to browse

Max 40MB

Paid plans from $39 raise this to 150 MB.

You can mix them

These aren't mutually exclusive. A common setup uses all three: the API powers your production app, the CLI runs nightly batch jobs in CI, and the MCP server lets your team spin up one-off flipbooks by asking an AI assistant. Same account, same flipbooks, same data — just different doors for different moments.

Same task, three ways

Here's the exact same outcome — create a flipbook from a PDF — through each door.

CLI — one command in your terminal:

fliplink flipbook create ./q3-report.pdf --title "Q3 Report" --name q3

API — an HTTP request you make from code:

curl -X POST 'https://go.fliplink.me/api/create-by-file' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -F 'File=@q3-report.pdf' \
  -F 'Name=q3' \
  -F 'Title=Q3 Report'

MCP — natural language in your AI client:

“Create a flipbook from q3-report.pdf titled ‘Q3 Report’.”

Behind the scenes the assistant calls the flipbook_create_by_file tool with the same parameters as the curl request above. All three return the same JSON — {"Result":"OK","ID":"90001","URL":"https://go.fliplink.me/view/<slug>", ...} — because all three hit the same endpoint.

Quick “pick one” guide

• Writing a script or a CI/CD pipeline? → CLI
• Building flipbooks into your own app? → API
• Want an AI assistant or a non-coder to do it? → MCP
• Not sure? Start with the CLI — it's the quickest way to see results, and what you learn maps directly onto the API.

Whichever door you walk through, you're using the same FlipLink engine. Pick the one that matches how you work today — you can always add another later.

Related Reading

• Getting Started with the FlipLink CLI
• Connect FlipLink to Claude with an MCP Server
• What Is an MCP Server?
• How to Use the FlipLink API for Custom Integrations
• Automation and Integrations
• API Access