Agent for the Agentless: Weftly Now Has a Chat Client (and Anyone Can Build Their Own)

Weftly Is a Platform, Not an App

Weftly began with a bet: video editing should be a set of tools an agent can call, not a timeline you drag things around on. Transcribe. Summarize. Find the good moments. Cut a vertical clip. Publish it. Each one a single MCP call, paid per job, no account and no subscription.

That bet still holds. But it came with an assumption baked in — that you already have an agent. Claude Desktop, Claude Code, Cursor, something that speaks MCP and that you’ve already set up. Plenty of people do. Plenty of people don’t, and telling them “first, install an MCP host” is a strange thing to say to someone who just wants a clip out of last week’s interview.

So we brought our chat client back. An “agent for the agentless” chat.weftly.ai

chat.weftly.ai

Open it in a browser, drop in a file, say what you want. The agent on the other side knows Weftly’s tools and drives them for you. No connector config, no JSON, no install. If you’ve never heard of MCP, you never need to.

It’s a genuinely nice way to work. Ask for a transcript and get one. Ask which three minutes of a 90-minute recording are worth posting, and the agent runs find_clips, reads the results back to you in plain language, and cuts what you pick. The source video stays in storage, so if you decided you want more clips, you don’t re-upload and don’t re-transcribe your video.

Through September, the promo code PEER-PUSH gets you free jobs. If you’ve been meaning to try it, you’ve got nothing to risk.

weftly-hermes, the Discord client

Here’s the part that matters more than the chat app itself.

You can build your own client for your own workflow, without having to build and pay for the video processing platform underneath.

Mike, our editor at The Woven Record, needed branded clips. Branding wasn’t in Weftly’s pipeline yet, and he shouldn’t have to wait on us to ship it or on me to run a Claude skill to do it for him. So, to unblock him, we built weftly-hermes: a Discord app backed by a container running hermes and ffmpeg. He posts a clip in a channel, it comes back branded. I use it now too, because it’s a dead simple (and fun) way to get branded clips.

It took part of a weekend. It is not a product. It is a client, built for Mike’s workflow, and to keep our team’s branding consistent.

Those custom branding skills are coming to Weftly proper soon. But hermes made the real point first, which is that nobody had to ask permission to build it. Weftly’s tools were already there and already callable. The interface was the only thing missing, and because Weftly’s interfaces are well defined, building on top of it as a Discord or Slack app is fairly easy.

Two clients, one platform

chat.weftly.ai and weftly-hermes have almost nothing in common. One is a polished browser experience for a first-time user. One is a Discord bot for a single editor in a two-person newsroom. Different users, different surfaces, different orchestration.

They call the same tools.

Weftly is not a video editor with an API bolted on the side. The tool surface is the product, and the client is a choice — ours, yours, or none at all if you’d rather just point Claude at it and skip the UI entirely. There are three ways to use Weftly today and they’re all first-class:

• Bring your own agent. Add Weftly as an MCP connector in Claude, Claude Code, Cursor, or any MCP host. This is still the most powerful way to use it, because your agent can chain Weftly with everything else it can reach.
• Use one of ours. chat.weftly.ai if you want a conversation. Hermes-style bots if you want the work to happen where your team already talks.
• Build your own. A CLI for your pipeline. A bot for your Slack. A web form your clients can use without knowing what a transcript job costs.

What it actually takes to build a client

Less than you’d expect, and that’s on purpose. The easiest way is to build on top of Weftly’s MCP server, but you can also call the Weftly APIs directly.

Payment is per job and happens inline. Calling a paid tool returns a payment challenge; browser-based hosts get a Stripe Checkout link and pay by card, agent hosts can sign it with USDC. Either way, the tool runs once it’s paid. Your client doesn’t need billing infrastructure because Weftly’s meter is attached to the call, not to a customer record you’re responsible for.

Jobs are two-phase. Initiate to get a job id and a payment link, pay, then resume with the job id and poll for status. Long jobs don’t hold a connection open, so a Discord bot and a browser tab and a shell script can all live with the same pattern without any of them pretending to be a long-running session.

And source reuse means a clip pipeline is cheap to build. Transcribe or find clips once, then pass that job id as the source for every cut you want. No re-upload, no re-transcribe.

Try it, then break it

Start at chat.weftly.ai with PEER-PUSH and see whether the workflow fits how you think about your footage. If it does, the more interesting question is what you’d build on top of it — because the tools that make the chat app work are the same ones sitting there waiting for whatever client you have in mind.

We’d like to see what you make. Come tell us at [email protected]