Using FlipLink in Cursor and Other MCP Clients

If you already live inside Cursor, you don't need to leave your editor to work with FlipLink. By adding the FlipLink MCP server, Cursor's built-in AI can create flipbooks, publish them, pull leads, and more — just by asking in plain language. The same config works in Claude Desktop, Codex, and any other tool that speaks the Model Context Protocol.

This guide walks through the Cursor setup, then shows you the generic config that works in every MCP client.

What an MCP Client Is

An MCP client is any application that can connect to MCP servers and let its AI use the tools those servers expose. Cursor, Claude Desktop, and Codex are all MCP clients. The Model Context Protocol is the open standard that lets them talk to a server like fliplink-mcp without any custom glue code.

When you connect the FlipLink MCP server, the client launches it in the background and the AI gains a set of FlipLink tools — things like flipbook_create_by_file, flipbook_publish, and leads_list. New to the concept? Start with what an MCP server is, then come back here.

Where Cursor's MCP Config Lives

Cursor manages MCP servers from its settings. Open Cursor's settings, find the MCP / Model Context Protocol section, and choose to add a new MCP server. Cursor lets you paste a server definition as JSON — the same mcpServers shape every MCP client uses.

You don't install anything by hand. The client runs the server with npx on demand, so the only prerequisites are Node.js 18+ and a FlipLink API key. Get a key by signing in at go.fliplink.me and opening the Subscription page.

The FlipLink Server Block

In Cursor's MCP settings, add an MCP server using this mcpServers entry. Replace <YOUR_KEY> with your FlipLink API key:

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

A few notes on this block:

• command + args tell the client to launch the server with npx — no global install needed.
• FLIPLINK_API_KEY authenticates every call. Treat it like a password; keep it out of shared repos.
• FLIPLINK_MCP_MODE controls how many tools are exposed. safe (the default) gives reads plus reversible writes and access controls — no deletes or commerce actions. Use readonly for a look-but-don't-touch setup, or full for everything. See MCP safety modes for the full breakdown.

After saving, restart Cursor (or reload the MCP server from settings) so it picks up the new entry.

Test It: Ask Cursor to Call whoami

The fastest way to confirm the connection works is the health-check tool. In Cursor's chat, ask:

Use the FlipLink MCP and call whoami.

The whoami tool is the top-level account check. If your key is valid, you'll get back your account identity and your maximum upload size. If the key is missing or wrong, the tool returns clear setup instructions instead of a cryptic error — that's your cue to fix the FLIPLINK_API_KEY value and restart.

Once whoami works, try something real:

Create a flipbook from ./deck.pdf titled "Q3 Report", then give me the share link.

Cursor's AI will call flipbook_create_by_file and flipbook_get_share_link for you, no manual API calls required.

🚀

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.

Other Clients Use the Same Config

The beauty of MCP is that the config is generic. The exact mcpServers block above works in Claude Desktop, Codex, and any other MCP client — only the menu where you paste it differs. In each client, look for the MCP or Model Context Protocol settings and add a server using that same JSON shape.

If your client offers a stdio transport option, that's the one to pick: fliplink-mcp communicates over stdio, which is exactly what command + args set up. There's nothing FlipLink-specific about the transport — it's the standard stdio config every MCP server uses.

For Claude Code specifically, you can skip the JSON entirely and run one command:

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

A dedicated walkthrough for that client lives in connect FlipLink to Claude with MCP.

Troubleshooting FAQ

Q: The FlipLink server doesn't show up in Cursor. What now? A: First confirm Node.js 18+ is installed (node --version), since npx needs it. Then double-check the JSON is valid — a missing comma or bracket will silently drop the server. Finally, fully restart the client so it re-reads the config.

Q: Tools appear, but every call fails with a setup message. A: That means the API key isn't reaching the server. Verify FLIPLINK_API_KEY is set in the env block and that the value is your real key from the Subscription page. Save and restart after editing.

Q: Why can't the AI delete a flipbook or run a sale action? A: You're in safe mode, which hides destructive and commerce tools by design. Switch FLIPLINK_MCP_MODE to full to enable them — but note that delete and money actions still require a confirmation step before they run. See MCP safety modes.

Wrapping Up

Adding FlipLink to Cursor takes one JSON block and a restart. Once it's wired up, your editor's AI handles flipbook creation, publishing, and lead exports through natural language — and the same config drops straight into any other MCP client you use.

Related Reading

• The FlipLink MCP server — full tool list, modes, and safety details
• What is an MCP server?
• Connect FlipLink to Claude with MCP
• MCP safety modes (readonly / safe / full)
• FlipLink CLI documentation
• API reference