Model Context Protocol

FlipLink MCP Server

Operate FlipLink from your AI assistant. Let Claude, Cursor, or any MCP-capable client create, configure, publish, and manage your flipbooks in natural language — with built-in guardrails on anything destructive.

Connect with one copy-paste

Copy the starter prompt into Claude Code — it adds the FlipLink MCP server and verifies it.

Mode

Replace YOUR_API_KEY with your actual FlipLink API key.

Set up and verify the FlipLink MCP server for me.

1. Add the server to this Claude Code session by running this in the terminal:
   claude mcp add fliplink -e FLIPLINK_API_KEY=YOUR_API_KEY -e FLIPLINK_MCP_MODE=safe -- npx -y fliplink-mcp

2. Confirm it was added: run `claude mcp list` and check that "fliplink" appears and shows as connected.

3. Verify the config: confirm the "fliplink" server has FLIPLINK_API_KEY set in its env (it must be my real
   key, not the YOUR_API_KEY placeholder, and must not be empty). Reading config: `claude mcp get fliplink`.

4. Test the connection: call the FlipLink "whoami" tool. If it returns my account, the MCP is live.

5. If "fliplink" is missing or won't connect, troubleshoot:
   - Ensure Node.js 18+ and npx are installed (`node -v`).
   - Re-run the add command and confirm FLIPLINK_API_KEY is present and correct (not the placeholder).
   - Remove and re-add: `claude mcp remove fliplink` then re-run step 1; restart the session.
   - Re-run `claude mcp list` to confirm it now shows connected.

Once "whoami" succeeds, list the FlipLink tools now available to you.
Get your API key

Works with your AI tools

  • Claude logoClaude
  • Cursor logoCursor
  • ChatGPT logoChatGPT
  • Codex logoCodex
  • VS Code logoVS Code
  • Windsurf logoWindsurf

Installs via npx fliplink-mcp · uses your own API key · 87 tools

How it works

The FlipLink MCP server is a small program your AI client runs on your machine. It exposes the same FlipLink REST API as MCP tools, so the assistant can call them in natural language. It is a third front door to the same API — a sibling of the CLI. Nothing about the API changes; this server is just another client, and all guardrails run locally before any request leaves your machine.

Install

You don't install anything by hand — your AI client launches the server with npx. You only need your own FlipLink API key (see below).

Claude Code

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

Claude Desktop · Cursor · Codex

Add this to the client's MCP config (an mcpServers block):

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

Get your API key

Each user supplies their own key — we never pre-fill one. Sign in and copy your key from the subscription page, then paste it into the config above as FLIPLINK_API_KEY.

Get your key →

If the key is missing, every tool returns clear instructions to add it — so the assistant can guide you through setup before you read any docs.

Starter prompt

Paste this into a new AI session to bootstrap a safe workflow:

prompt
You now have the FlipLink MCP server connected (tools like whoami,
flipbook_create_by_file, leads_list). First, call whoami to confirm my account is reachable.
If it returns an auth error, ask me to paste my FlipLink API key (I get it from
https://go.fliplink.me/Subscription) and remind me to put it in the MCP server config as
FLIPLINK_API_KEY, then stop until I confirm.
Once connected you can create, list, and configure my flipbooks. For any delete, sale/pricing,
or access-control change, show me a one-line preview and wait for my explicit "yes" before doing it.
Here's what I want to do: <describe your task>

Modes

Tools are tiered by risk, and a mode decides which tiers are exposed. Set FLIPLINK_MCP_MODE in the config (defaults to safe).

ModeExposesNotes
readonlyReads only (19 tools)whoami, lists, lookups
safe (default)Reads + reversible writes + access-control (79 tools)No delete or commerce tools
fullEverything (87 tools)Delete + commerce tools require confirmation

New to the terms? See what an API is and automation.

Safety model

In full mode, destructive (delete) and money (sale / pricing) tools never run on the first call. The server returns a one-line preview and a short-lived confirm_token; the assistant must show you the preview and call again with that token. The token is bound to the exact arguments and expires in 5 minutes. This gate lives in the server — the FlipLink API never sees it.

Every tool also carries MCP annotations (readOnlyHint, destructiveHint, idempotentHint) so clients can show their own approval prompts.

Tools

Tools are generated from the API spec and named <noun>_<verb> — for example flipbook_publish, flipbook_set_skin, leads_list, cname_add. The one top-level health-check tool is whoami. For the full parameter reference of every underlying endpoint, see the REST API docs.

Frequently asked questions

What is an MCP server?

An MCP (Model Context Protocol) server is a small program your AI client runs locally that exposes tools to the assistant. FlipLink's server exposes the same FlipLink REST API as tools, so Claude, Cursor, or any MCP client can create, configure, and publish flipbooks in natural language.

Which AI clients are supported?

Any MCP-capable client — including Claude Code, Claude Desktop, Cursor, and Codex. You add FlipLink to the client's mcpServers config and it launches the server on demand with npx fliplink-mcp.

What are the readonly, safe, and full modes?

Modes decide which tools are exposed. readonly exposes 19 read-only tools; safe (the default) adds reversible writes and access-control for 79 tools; full exposes all 87, with delete and commerce tools gated behind a confirmation step. Set the mode with FLIPLINK_MCP_MODE.

Is it safe to let an AI manage my flipbooks?

Yes. In full mode, destructive (delete) and money (sale / pricing) actions never run on the first call — the server returns a one-line preview and a short-lived confirm token bound to the exact arguments, and the assistant must confirm before anything happens. The guardrails run locally; the FlipLink API is unchanged.

Do I need my own API key?

Yes — each user supplies their own key from the FlipLink subscription page, set as FLIPLINK_API_KEY in the config. If the key is missing, every tool returns clear setup instructions so the assistant can guide you through it.