How to Connect FlipLink to Claude with the MCP Server

What if you could just ask Claude to — “turn this PDF into a flipbook and publish it” — and it actually did? That's exactly what the FlipLink Claude MCP server makes possible. Once it's connected, Claude can create, list, publish, and manage your flipbooks through natural conversation, no clicking through the dashboard required.

This guide walks you through the whole setup — under five minutes from start to first task.

What You'll Need

Before you connect anything, make sure you have:

• Node.js 18 or newer — the server runs through npx, so Node is the only runtime dependency. (You don't install the server by hand; your AI client launches it on demand.)
• A FlipLink API key — sign in at go.fliplink.me and grab your key from the Subscription page. This key authenticates every action Claude takes, so treat it like a password.

That's it. If you've never used a model context protocol server before, it's worth a two-minute read: what is an MCP server.

Connect FlipLink to Claude Code (One Command)

If you use Claude Code, the entire setup is a single command. Drop in your key and run:

claude mcp add fliplink -e FLIPLINK_API_KEY=<YOUR_KEY> -- npx -y fliplink-mcp

That registers FlipLink as an MCP server, passes your API key in as an environment variable, and tells Claude to launch the server through npx whenever it needs it. The -y flag lets npx fetch the package without an interactive prompt. Restart your Claude Code session and FlipLink's tools become available.

Connect Claude Desktop (Config Block)

Claude Desktop (and other clients like Cursor or Codex) use a JSON config instead. Add an mcpServers entry like this:

{
  "mcpServers": {
    "fliplink": {
      "command": "npx",
      "args": ["-y", "fliplink-mcp"],
      "env": { "FLIPLINK_API_KEY": "<YOUR_KEY>", "FLIPLINK_MCP_MODE": "safe" }
    }
  }
}

Swap <YOUR_KEY> for your real key, save the config, and restart the client. On the next launch, the FlipLink tools load automatically. The FLIPLINK_MCP_MODE value sets which actions are allowed — more on that below.

Verify the Connection

Before you ask Claude to do real work, confirm everything is wired up. The simplest check is the top-level health tool, whoami. Just ask Claude:

“Run the FlipLink whoami tool.”

Claude calls the tool and returns your account identity and your maximum upload size. If your key is missing or wrong, the server replies with clear setup instructions instead — so a confusing error becomes a fixable one.

🚀

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.

What a Tool Call Looks Like

You never type a tool name yourself. You describe what you want in plain language, and Claude picks the right tool, fills in the arguments, and runs it. FlipLink's tools are generated straight from the API spec and named <noun>_<verb> — so you'll see calls like flipbook_create_by_file, flipbook_publish, flipbook_set_skin, or leads_list go by as Claude works.

Behind the scenes each tool maps to a real FlipLink API endpoint. If you ever want to see the underlying request shapes, parameters, and a live Try-It console, the full API reference documents every one — and that's also where your API key comes from.

Your First Task

Now the fun part. Hand Claude a PDF and ask:

“Create a flipbook from this PDF and call it Q3 Report.”

Claude calls flipbook_create_by_file, uploads the file, and hands back the new flipbook's ID and share URL. From there you can keep going in the same conversation:

“Now publish it and give me the share link.”

Claude chains flipbook_publish and flipbook_get_share_link and returns a link you can send out immediately. No tab-switching, no manual steps — just a conversation that produces real, published flipbooks. For the broader picture of what this unlocks, see natural-language flipbook automation.

A Word on Modes (Safe by Default)

The MCP server ships with a guardrail you should understand: the FLIPLINK_MCP_MODE setting controls which tools Claude can reach.

• readonly — 19 tools, reads only. Claude can list and inspect, but never change anything.
• safe — 79 tools and the default. Reads plus reversible writes and access control; no delete, no commerce actions. This is the right starting point for almost everyone.
• full — all 87 tools, including destructive and money-related actions.

Even in full mode there's a second safety net: delete and sale/pricing tools never fire on the first call. The server returns a one-line preview plus a short-lived confirmation token (bound to those exact arguments, expiring in five minutes), and Claude has to show you the preview and call again with the token before anything irreversible happens. If you want the full breakdown of how these guardrails work, read MCP server safety guardrails.

Start Talking to Your Flipbooks

Connecting FlipLink to Claude turns flipbook management into a conversation. One command (or one config block), a quick whoami check, and you're asking Claude to build and publish flipbooks for you — safely, with safe mode protecting you out of the box.

Ready to go? Get your key from the Subscription page, run the setup command, and ask Claude to make its first flipbook.

Related Reading

• FlipLink MCP server overview
• What is an MCP server?
• MCP server safety guardrails (readonly / safe / full)
• Natural-language flipbook automation
• API Access feature
• FlipLink CLI reference