Uoink

Uoink

A YouTube transcript MCP server that remembers. Uoink saves YouTube videos, podcasts, X posts, Reddit threads and web pages with their full transcripts to a library on your computer. Claude, Cursor or Codex then searches all of it and cites the exact timestamp.

Free and open source (MIT). Windows 10/11 and Mac (Apple silicon, macOS 15+). Linux desktops and headless sandboxes use the Linux install. No account, no Uoink cloud. Videos without captions are transcribed on your machine with Whisper.

Quick start

1. Install: download from [uoink.app/get](https://uoink.app/get), or on a Mac run brew install --cask ryanbiddy/uoink/uoink. For Linux, see the Linux guide.
2. Connect your AI: uoink connect claude-code. For other clients run uoink connect --list; Claude Desktop can use the .mcpb extension from the latest release.
3. Ask: *"uoink https://youtu.be/… and tell me where they explain the eval setup."* Later: *"which of my saved talks disagreed about that?"*

Your AI gets the quote and the minute, not a guess. Every saved source stays on disk as Markdown and JSON you can open yourself.

• Website: https://uoink.app · Developers: https://uoink.app/developers · Also listed on mcpservers.org and the official MCP registry.
• Good to know: the Windows installer is unsigned, so SmartScreen asks first (choose More info → Run anyway). The browser extension loads from the app's setup screen; it isn't on the Chrome Web Store yet. Anonymous usage counts stay off unless you turn them on.

If Uoink saves you time, a ⭐ helps other people find it.

Why Uoink

You see a video that's clearly working and you want to know why. So you paste the YouTube link into Claude and hope it can "watch" it. It can't — it hallucinates the quotes, invents the title, and gives up past the first paragraph. You end up watching the whole thing on 2x, taking notes by hand.

Uoink fixes that. Click the Uoink button under any video (or right-click a link, or press Alt+U) and you get the full transcript, timestamped screenshots, top comments, channel context, and metadata — copied to your clipboard and saved on disk, ready for Claude, ChatGPT, or your notes app. Or tell your AI agent *"uoink that video and decode the hook"* and it does both, with no clipboard step.

The corpus compounds. Every source you save lands in one local library your AI can search, cite, and write from — in your voice.

What you can capture

Published sources are indexed in one local library. Podcast audio and transcripts stay under Uoink's local data folder; publishing an episode adds its Markdown and sidecar to that same searchable index.

Three ways your AI reads the corpus

1. Clipboard (the creator path) — Click Uoink, paste into Claude / ChatGPT. Transcript plus a paste-safe subset of screenshots inlined as images so the model sees text *and* frames in one paste.

2. MCP server (the agent path): A local MCP server exposing 99 tools over stdio, five library resource templates and ten prompts. Claude Desktop (.mcpb), Claude Code and Cursor get the full capture, research, writing and Library tool set through the standard connection. Consent gates are unchanged.

The stdio transport is tested with Claude Desktop and Cursor. Cline and Continue are standard-stdio compatibility paths, not individually smoke-tested.

• stdio defaults to all 99 registry tools. UOINK_MCP_TOOLSET=research serves research_start, research_discover, research_capture, research_status, research_evidence, research_publish and uoink_url to discover, capture, retrieve evidence and publish verified reports. Set UOINK_MCP_TOOLSET=core in the client's environment for the 36 core tools (the earlier 35 plus get_transcript). Cursor and other clients with tool caps may need this setting. Restart the connection after changing it.
• HTTP JSON-RPC at /mcp/v1 exposes the same 99-tool registry through the token-authenticated local helper. Both MCP transports share handlers and flatten the same three top-level oneOf input schemas for client compatibility. The server still validates the exact frozen schemas.
• [Video deep research](docs/research.md): find sources, capture transcripts and publish timestamped receipts through the CLI or dashboard Research tab.

3. OpenAPI bridge (for local agents that don't speak MCP) — Local OpenAPI-capable agents and scripts can drive the same tools over an OpenAPI 3.1 surface at /openapi/v1/spec.json + POST /tools/ .

Use Uoink from any AI agent

After installing, open a new terminal and run uoink status or uoink search "working memory" --limit 5. The installer's checked PATH option makes uoink available to agents with a local shell. uoink connect prints connection instructions for MCP clients.

The portable skill supports Claude Code, Codex, pi, Hermes Agent, and OpenClaw through MCP or the CLI. The Claude Code marketplace at ryanbiddy/uoink-agent-kit, published with this release, bundles the skill and MCP config. See Connect your agent for commands and client limits, or agent installation steps for installation from a shell.

MCP setup (Claude Desktop, Cursor, Cline)

After installing Uoink, open the setup page from the extension popup's Settings link and copy the generated snippet — or paste this into your client's MCP config. The stdio server runs the bundled Python against the installed uoink_mcp.py (the C-01 fix pins the app dir onto sys.path, so this command works on every install):

{

"mcpServers": { "uoink": { "command": "%LOCALAPPDATA%\\Uoink\\python\\python.exe", "args": ["%LOCALAPPDATA%\\Uoink\\uoink_mcp.py"] } } }

Claude Desktop does not expand %LOCALAPPDATA% — use the full absolute path (e.g. C:\\Users\\ \\AppData\\Local\\Uoink\\python\\python.exe). Restart the client after saving; Uoink's tools appear automatically.

Uoink 3.12.1 and later add a portable launch line that needs no install path: "command": "uoink", "args": ["mcp"], or "command": "cmd", "args": ["/c", "uoink", "mcp"] for Windows clients that cannot start .cmd files. It uses the uoink command on PATH. See Connect your agent.

One-click install: a Claude Desktop .mcpb bundle installs the stdio server without hand-editing config. See docs/mcpb-bundle.md.

HTTP transport: point an HTTP MCP client at http://127.0.0.1:5179/mcp/v1 and send the header X-Uoink-Token (read the token from %LOCALAPPDATA%\Uoink\token.txt).

Uoink Operator Skill

Uoink ships a portable Skill at skills/uoink/SKILL.md (installed to %LOCALAPPDATA%\Uoink\skills\uoink\) for finding saved evidence, citing timestamps, capturing URLs, saving notes, and writing from the user's sources and voice. Clients that support Agent Skills can load the same file alongside Uoink's MCP tools or use its exact CLI commands. See Connect your agent for install paths and the small Claude Code plugin kit.

Install

1. Download the installer. Download Uoink-Setup-3.14.1.exe from the v3.14.1 release. For Windows 10/11; Mac steps are below. The installer is unsigned: if SmartScreen shows "Windows protected your PC", choose More info -> Run anyway, and check the file against the SHA-256 listed on the release page.
2. Run it. Defaults install to %LOCALAPPDATA%\Uoink\ (no admin required). The finish page can launch the helper immediately, and an autostart entry runs it on each login.

1. Load the bundled extension. On first launch, Uoink shows a one-time setup splash. Use it to open your browser's extensions page and copy the installed extension path; then enable Developer mode, click Load unpacked, and select that folder.

On a Mac (Apple Silicon, macOS 15 or later; preview): download Uoink-3.14.1-macos-arm64.dmg from the same release, drag Uoink to Applications, eject the disk and open Uoink from Applications. The app is signed and notarized, so macOS only asks its usual question about apps downloaded from the internet. Then load the extension from the setup splash as above. See docs/mac/INSTALL.md.

The store install link is controlled by store-config.json. When the listing is live, the setup splash and these steps offer Add to Chrome, with sideloading under Advanced. Release maintainers: follow SUBMIT-NOW.md.

On Linux, including Docker and headless agent sandboxes, see docs/linux.md.

git clone https://github.com/ryanbiddy/uoink && sh uoink/scripts/linux/install.sh

For developers running from source, see REQUIREMENTS.md. Build the installer locally with ./build.ps1 (see docs/build-installer.md).

Quiet desktop notifications

Desktop notifications are on by default. To keep background feed watches and captures invisible, open Dashboard → Settings → Local app and turn off Show desktop notifications. Uoink keeps suppressed updates in the dashboard's Activity view, so silence does not discard the event. Uoink also applies the same courtesy automatically while a foreground app covers its monitor, including borderless and exclusive-fullscreen games.

The persisted setting is notifications_enabled in settings.json. Local clients can read it through GET /settings or update it with an authenticated POST /settings body such as {"notifications_enabled": false}. Restart is not required.

Phone inbox (optional)

Share a link from your phone's share sheet and Uoink captures it on your computer, with no phone app. Deploy a small relay to your own Render account, point an iOS Shortcut or Android share target at it, then add it in Settings > Capture > Phone inbox. The relay holds only the link and an optional note, until Uoink picks it up or for 7 days at most.

Setup, the Shortcut recipe and the free-plan tradeoffs are in docs/relay.md.

How it works

Extension flow: click Uoink under a video → Uoink extracts transcript, screenshots, comments, metadata → Markdown corpus lands on your clipboard (screenshots embedded) and the full set saves to disk → paste, run a prompt,