Your Reels, TikToks, YouTube videos, repos, web pages and voice notes, put to work.

Drop a link. Sopie keeps one clean entry per tool or technique, ready for your AI agents over MCP.

You are on the list. We will write to you when Sopie is ready for you.

Sopie isn't released yet. The waitlist is free.

How it works

Every source has its own colour

  • Instagram Reels
  • GitHub repos
  • Voice notes
  • TikTok
  • Docs
  • READMEs
  • YouTube
  • Blog posts
  • Threads

Watch it once. Your agents remember.

Three steps, and only the first one is yours.

  1. Drop it in

    Share a Reel, a TikTok, a YouTube link, a GitHub repo or a web page, or record a quick voice note. No tags, no folders.

    Video Repo Web page Voice note
  2. Sopie keeps one entry

    Sopie works out which tool or technique a source is about. If you already have an entry for it, the new source joins that entry instead of making a copy.

  3. Your agent asks first

    Before Claude Code, Cursor or Codex goes searching the web, it asks Sopie over MCP: do we already have something for this? It gets the entry, its sources and what it connects to.

Five saves, four kinds of sourceMerged into one entryYour agent asks, Sopie answers

Example

AgentDo we already have something for browser automation?

Playwright MCP

tool

Lets an agent drive a real browser: open pages, click, type and read what is on screen.

Sources
  • replaceshand-written browser scripts
  • needsNode.js
  • pairs witha screenshot review skill

One entry. Everything your agent needs.

Not a feed of saved posts. A small, tidy registry that answers questions.

Ask over MCP or the API

Your agent sends a plain question and gets back structured entries it can act on, with the sources attached.

Example query and answerExample
// an agent asks before it searches the web
sopie.search({ query: "browser automation", kinds: ["tool", "technique"] })

// answer
{
  name: "Playwright MCP",
  kind: "tool",
  summary: "Lets an agent drive a real browser.",
  sources: [
    { type: "github", url: "https://github.com/microsoft/playwright-mcp" },
    { type: "reel", saved_from: "Instagram" }
  ],
  pairs_with: ["screenshot review skill"]
}

One entry per tool

Saw the same tool in a Reel, a TikTok and a repo? That is one entry with three sources, not three bookmarks.

Example
  • Reel: this MCP lets Claude use ChromeInstagram
  • TikTok: stop writing Selenium by handTikTok
  • microsoft/playwright-mcpGitHub
  • Playwright MCPone entry

Every entry links back

Each entry keeps the links to the Reels, repos, pages and notes it came from, so you and your agent can always check the original.

Relations, not folders

Entries know what they replace, what they need and what they pair well with. Your agent gets the neighbours, not just the match.

Portable as SKILL.md

Take any entry out as a plain SKILL.md file your agent can load. Your library stays yours, in an open format.

For the things you meant to try.

Four ordinary saves, and what your agent can do with them later.

From a Reel

The tool someone demoed between two memes.

You do
Share the Reel to Sopie while you scroll. That is all.
Sopie keeps
An entry for the tool it shows, a short summary and a link back to the Reel.
Later, your agent
Finds it when you ask for the same job, instead of guessing a library from the web.

From GitHub

The repo you starred and never opened.

You do
Paste the GitHub link.
Sopie keeps
What the repo is for, what it needs to run and a link to its README.
Later, your agent
Hears it exists before it writes the same thing from scratch.

From a voice note

The idea you had on a walk and lost by dinner.

You do
Record a note: try screenshot diffs on the dashboard.
Sopie keeps
The technique in plain words, linked to your note.
Later, your agent
Gets it back when it asks about visual testing.

From a web page

The clever trick buried in a long thread.

You do
Save the page or the thread link.
Sopie keeps
Just the trick, as a technique entry, joined to any tool it uses.
Later, your agent
Gets the trick and the tool together, with the page to check.

Questions, answered.

What is Sopie, in one line?

A registry for the tools and techniques you come across. You drop in links and voice notes; Sopie keeps one clean, source-linked entry per tool or technique, and your AI agents can ask it what you already have.

Which sources can I add?

Instagram Reels, TikTok and YouTube videos, GitHub repositories, web pages and your own voice notes.

Does Sopie keep copies of the videos?

No. The plan is to keep what a source is about and a link back to it, not the clip itself. The original stays where it was posted.

Which agents can use it?

Any agent that speaks MCP, such as Claude Code, Cursor or Codex. There will also be a plain HTTP API for everything else.

What if I save the same tool twice?

The new source joins the entry you already have. You end up with one entry and more sources, not a pile of duplicates.

When can I use it, and what will it cost?

Sopie is not released yet. Joining the waitlist is free, and we will write to you when it is ready for you. Pricing will be published before launch, on the pricing page.

Can I delete what I saved?

Yes, that is the plan: you will be able to delete any entry, or everything, whenever you like.

Your agents could already know this.

Join the waitlist and we will write to you when Sopie is ready for you.

You are on the list.

Thanks. We will write to you when Sopie is ready for you.