flipletters-mcp-server

MCP server that lets AI agents draft, validate, and share FlipLetters split-flap video boards as flipcode — so an agent on your team can prepare board drafts and hand its manager a link that opens the exact board in the Studio.

Everything is local computation on the open @flipletters/flipcode parser: no network calls, no credentials, nothing destructive.

Tools

| Tool | What it does | |---|---| | flipletters_flipcode_reference | The flipcode cheat sheet — call before writing a board | | flipletters_example_board | A known-good board file for any board type, to edit rather than write from scratch | | flipletters_validate_board | Parse a draft: normalized code + warnings + summary + a share URL that opens the board in the Studio | | flipletters_template_url | Build a human-readable ?board=…&slide=… Studio URL for short text boards |

The intended agent loop: reference → write flipcode → validate (fix warnings) → deliver the share link. The human opens it, previews with sound, tweaks anything in the editor, and exports.

Setup

cd packages/flipcode && npm install && npm run build
cd ../flipletters-mcp-server && npm install && npm run build

Claude Code / Claude Desktop config:

{
  "mcpServers": {
    "flipletters": {
      "command": "node",
      "args": ["/path/to/packages/flipletters-mcp-server/dist/index.js"]
    }
  }
}

Set FLIPLETTERS_STUDIO_URL to point links at a non-production Studio.

Roadmap

• Render tool (flipletters_render_board) — MP4 rendering via an API-key-metered endpoint, so agent renders are billable usage (Stripe metered billing; the key owner pays).
• Team tools (flipletters_share_to_team) — share a validated board straight into a Team Library once API-key auth exists server-side; today the agent's share link does the same job manually.

License

MIT