Quicly

live.quiclyPublished by quicly.liveOfficial publisherv0.2.1Updated Oct 24, 2026

Put a live video feed on air and get a URL you can embed.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Quicly is a remote MCP server that lets an assistant put a live video feed on air and get an embeddable URL.

What you can do
Publish a live video feed and take it on air through the connected service. Retrieve a URL for the live feed that can be embedded elsewhere. Tool-level details are not published, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to help start a live video broadcast and obtain an embeddable link for a page or app, rather than editing video files.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and is required, so the user must sign in to the Quicly service.
Before you install
The server requires OAuth sign-in, so it receives account access through that authorization. It publishes live video on air, which is a public-facing action that may be hard to undo; confirm before going live. The feed and its embed URL are hosted by a third party.

Installation

In SourceWeft

  1. Open Quicly in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/live.quicly%2Fquicly/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "quicly": {
      "type": "http",
      "url": "https://api.quicly.live/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.