Slidesfly integrations for Agents, GitHub Actions, and apps

Choose the shortest integration path

CI/CDGitHub ActionsPublish or update a built HTML deck from a repository workflow.Coding AgentAgent SkillGive Codex, Cursor, or Claude Code a precise, reusable publishing contract.Agent toolHosted MCPGive an MCP-compatible host a remote deck-publishing tool with account ownership.Custom productOpenAPIBuild a first-party workflow directly against the Slidesfly HTTP contract.

Your workflow	Recommended interface	Why
A deck is built in a GitHub repository	GitHub Action	Publish on push, release, or manual dispatch without a separate deploy project.
A coding Agent creates the local artifact	Agent Skill plus CLI or MCP	Keep the trigger, secret handling, verification, and handoff behavior together.
An Agent host already supports remote MCP	Hosted MCP	Use typed tools without installing a local package.
Your own app owns the workflow	OpenAPI	Control authentication, idempotency, publishing, and error handling directly.

Publish from GitHub Actions

The root Action is a public beta and is listed on GitHub Marketplace. Add a Slidesfly API key as a repository or environment secret, then publish the generated deck from a workflow.

- id: deck
  uses: rare/slidesfly-integrations@v0.2.0
  with:
    file: deck.html
    api-key: ${{ secrets.SLIDESFLY_API_KEY }}
    visibility: unlisted

Review the GitHub Marketplace listing before adding it to a production workflow.
Store the API key in GitHub Secrets; never commit it in workflow YAML.
Pin a reviewed release tag or commit SHA when your supply-chain policy requires it.
Read the Action output instead of constructing a Slidesfly reader URL yourself.

Install the Agent Skill

The public repository includes the official Slidesfly Skill. Install it when the Agent that generates the deck should also know when and how to publish the finished artifact.

npx skills add rare/slidesfly-integrations --skill slidesfly

The website-installed Slidesfly CLI can also install the canonical Skill for supported runtimes:

curl -fsSL https://slidesfly.com/install.sh | sh
slidesfly install --target auto --scope user --json

Connect the hosted MCP server

Use the hosted Streamable HTTP endpoint when an MCP-compatible Agent host needs typed publish, list, versions, restore, claim, and status tools. Create an API key in Slidesfly account settings and keep it in the host's secret mechanism.

{
  "url": "https://slidesfly.com/api/mcp",
  "headers": {
    "Authorization": "Bearer sk_..."
  }
}

The repository contains the published MCP Registry metadata and a static capability card; the server itself remains hosted by Slidesfly. See the MCP reference for tools and authentication.

Build a direct OpenAPI integration

Use the HTTP API when your product needs to control the request lifecycle itself. Start from the canonical OpenAPI document, send a Slidesfly API key as a Bearer token, and use an Idempotency-Key for retried publish requests.

Choose ownership and visibility
Decide whether the deck is an anonymous first publish or an account-owned artifact, and whether its reader should be unlisted or public.
Send the artifact and stable retry key
Upload the finished HTML or eligible zip and preserve the idempotency key across safe retries.
Use and verify the returned URL
Treat the response as authoritative, then open the reader and test assets, navigation, and access before handing the link to a user.

Read the OpenAPI integration guide for authentication, request limits, errors, and update behavior.

Start from a verified framework fixture

The public repository includes fixtures for Plain HTML, Codex-generated HTML, Reveal.js, Slidev, and Marp. Each example links to a public Slidesfly reader that was verified on July 29, 2026.

Fixture	Packaging shape	Use it to verify
Plain HTML	Self-contained file	The smallest anonymous or owned publish path
Codex-generated	Self-contained file	An Agent-created artifact handoff
Reveal.js	Multi-file build	Runtime, theme, plugin, and local asset packaging
Slidev	Static build	Relative assets, storage fallback, and reader navigation
Marp	Self-contained export	CLI export and single-file publishing

Check the framework matrix before packaging a new integration.

Inspect, contribute, and help others trust the integration

The public repository is where developers can review implementation details, report reproducible issues, improve examples, and propose support for another framework or Agent host. Before relying on a public-beta integration in production, read its maintenance, contribution, and security policies.