Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Turn long videos into captioned, reframed short clips, thumbnails, and social posts.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://frameos.studio/mcpRun this in your terminal
claude mcp add --transport http frameos https://frameos.studio/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"frameos": {
"url": "https://frameos.studio/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"frameos": {
"type": "http",
"url": "https://frameos.studio/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://frameos.studio/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain frameos.studio (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Turn your long videos into short clips by asking the AI agent you already use. Paste a podcast, stream, interview or webinar link into Claude, ChatGPT, Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI or Perplexity, and FrameOS finds the strongest moments, reframes them for your format, adds captions and hands you back a ranked list of clips. You stay in charge of what gets exported, captioned, thumbnailed and posted.
This repo holds the FrameOS plugin, skills and extension packages. They connect your agent to the hosted FrameOS connector (an MCP server at https://frameos.studio/mcp) and teach it how to use FrameOS well: when to check your credits, how long to wait for a render, which caption styles exist, and never to post anything without your go-ahead.
Status, 2026-10-26: the hosted connector is live, and every listed app except Devin can sign in.
https://frameos.studio/mcpis up. Claude Code, Claude (web, Desktop, mobile), ChatGPT, Codex, Cursor and VS Code with GitHub Copilot are tested end to end against a real account; Gemini CLI, Perplexity and the Copilot CLI can sign in but are not tested end to end yet (beta). Devin (including Windsurf) is coming soon: it can't sign in yet. See docs/status.md for what is left, and try the whole workflow against the mock server without spending credits.
You don't need to learn any commands. Talk to your agent the way you'd brief an editor:
More ready-to-use prompts, grouped by job, are in docs/workflows.md.
Pick your app. Each guide has the exact steps, how to check it worked, how to sign in again, and known limits. Claude Code, Claude (web, Desktop, mobile), ChatGPT, Codex, Cursor and VS Code are tested end to end; Gemini CLI and Perplexity (since 2026-10-08) and the Copilot CLI (since 2026-10-23) can sign in but are not tested end to end yet; Devin is coming soon (status).
| Where you use AI | Quickest path | Full guide |
|---|---|---|
| Claude Code | claude mcp add --transport http -s user frameos https://frameos.studio/mcp then claude mcp login frameos (tested). Or, with the skills: claude plugin marketplace add theSatvik/frameos-plugins then claude plugin install frameos@frameos (signing in through the plugin's own connection is not tested yet) | docs/install/claude-code.md |
| Claude.ai, Claude Desktop, Cowork | Add a custom connector with https://frameos.studio/mcp (tested). Or, with the skills: Customize > Plugins > Add > Add marketplace, enter theSatvik/frameos-plugins (not tested yet) | docs/install/claude-ai.md |
| Codex | codex plugin marketplace add theSatvik/frameos-plugins then codex plugin add frameos@frameos | docs/install/codex.md |
| ChatGPT | Turn on developer mode, then add https://frameos.studio/mcp under ChatGPT Plugins | docs/install/chatgpt.md |
| Cursor | One-click install link (tested), or the plugin as a local plugin | docs/install/cursor.md |
| Gemini CLI | gemini extensions install https://github.com/theSatvik/frameos-plugins | docs/install/gemini-cli.md |
| VS Code and GitHub Copilot | VS Code: add https://frameos.studio/mcp to your mcp.json (tested), or Chat: Install Plugin From Source. Copilot CLI (1.0.83 or newer): copilot mcp add --transport http frameos https://frameos.studio/mcp, then /mcp auth frameos (not tested end to end yet) | docs/install/vscode-copilot.md |
| Perplexity | Account settings > Connectors > + Custom connector > Remote with https://frameos.studio/mcp | docs/install/perplexity.md |
| Devin and Windsurf (now Devin Desktop) | Coming soon: Devin can't sign in to FrameOS yet. Email support@frameos.studio to hear when it can | docs/install/devin-windsurf.md |
| Any other agent | npx skills add theSatvik/frameos-plugins, plus the connector URL https://frameos.studio/mcp | docs/install/other-agents.md |
Check it worked. In a new conversation, ask: "What is my FrameOS credit balance?" You should get your workspace name and a credit number. A "connected" badge on its own isn't proof; only a real answer is.
Let your agent do the install. Agents that can run commands (Claude Code, Codex, Gemini CLI and similar) can install FrameOS for you. Paste this:
Install FrameOS by following https://github.com/theSatvik/frameos-plugins/blob/main/docs/install-protocol.md
Your agent can:
Not available through your agent (use the FrameOS web app at https://frameos.studio/dashboard, or it's not available yet):
Clips made on the free plan carry a FrameOS watermark.
https://frameos.studio/mcp, and at FrameOS sign-in, https://clerk.frameos.studio, which you see once when you connect your account. Upload and download links that the connector hands back (for a file you ask your agent to upload, or a finished MP4) point at FrameOS's own file storage and expire.dev/, scripts/, tests/ and evals/ folders are maintainer tooling (a local mock server that runs only when you start it and calls nothing outside your machine, plus checks and tests); the plugin never runs them. In apps that can run commands, the skills may have your agent check and upload a video file you picked, wait between render checks, save an MP4 you asked for, or run your app's install steps when you ask it to set FrameOS up.X-FrameOS-Plugin-Version header in apps that support it.What FrameOS does with your videos and account is in the privacy policy and the terms. Questions: support@frameos.studio.
The repo ships a local mock FrameOS server with the same 27 tools and inputs as the real one, and errors in the same format. It needs no account, no sign-in and no credits, so you can watch the whole flow - submit, poll, clips, captions, export, thumbnails, copy and a fake post - without touching a real account.
git clone https://github.com/theSatvik/frameos-plugins
cd frameos-plugins uv run --script dev/mock_server.py # stdio uv run --script dev/mock_server.py --http --port 8790 # Streamable HTTP at http://127.0.0.1:8790/mcp claude --plugin-dir . --mcp-config dev/mock.mcp.json --strict-mcp-config # Claude Code: these skills + the mock only
Mock links point at mock.frameos.invalid, so nothing real is created. dev/README.md has the full walkthrough and the inputs that trigger each error.
The repo root is the plugin. One set of skills serves every host; each host reads its own manifest.
| File or folder | What it is | Read by |
|---|
| skills/ | The eight skills: frameos-setup, frameos-clip, [frameos-captions](skills/frameos-caption
Only the beginning is shown; read the rest in the repo