Sopie Join the waitlist
For agents

Your agents ask Sopie first.

Over MCP or a plain HTTP API, an agent can check what you have already saved, with the sources attached, before it spends time on a web search.

Join the waitlist See an example

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

Example: an agent asks first

AgentDo we already have something for browser automation?

Sopie: yes, Playwright MCP

One question in. One entry out.

Send a plain question. Get back a structured entry the agent can act on, with every source attached.

Illustrative only. Tool names, endpoints and fields are not final, and Sopie is not released yet.

Over MCP

Ask in plain words.

Add Sopie to your agent as an MCP server. It shows up as a tool the agent can call before it goes looking elsewhere.

Example tool callExample
// the agent calls a tool on the Sopie server
{
  tool: "search_entries",
  arguments: {
    query: "browser automation",
    kinds: ["tool", "technique"]
  }
}

Over HTTP

No MCP? Send a request.

For scripts and tools that do not speak MCP, the same question goes over a plain HTTP API and comes back as JSON.

Example requestExample
// the same question, as a plain request
POST /v1/search
Authorization: Bearer YOUR_KEY
Content-Type: application/json

{ "query": "browser automation" }

What comes back

An entry, not a list of links.

The agent gets what the tool is, where it came from and what it connects to, so it can act without another search.

Example answerExample
// one entry, with its sources
{
  name: "Playwright MCP",
  kind: "tool",
  sources: [
    { type: "github" },
    { type: "reel" },
    { type: "docs" }
  ],
  needs: ["Node.js"],
  skill_file: "playwright-mcp/SKILL.md"
}

Every entry can be a SKILL.md.

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

An entry, as a file

One folder, one SKILL.md. A short description up top, then what the tool is for and where it came from.

Example SKILL.mdExample
---
name: playwright-mcp
description: Lets an agent drive a real browser.
---

# Playwright MCP
Use it when a task needs a real browser:
open pages, click, type, read the screen.

Needs   Node.js
Sources GitHub repo, Reel, docs page

What the file holds

Plain text in an open format. Move it, edit it, keep it.

  • HeaderThe name and a one-line description
  • When to useThe situation the entry is for
  • NeedsWhat has to be installed first
  • SourcesLinks back to the Reel, repo or page

Built for the agents you already use.

Any client that speaks MCP can connect the same way. Everything else can use the HTTP API.

Sopie is not released yet. These are the clients we are building for.

Claude Code

Add Sopie as an MCP server and let Claude Code check your entries before it searches.

Over MCP

Cursor

Connect the same server in Cursor, so your saved tools show up while you code.

Over MCP

Codex

Point Codex at Sopie and it can ask what you already have before it writes something new.

Over MCP

Any MCP client

Anything that speaks the Model Context Protocol can connect and ask the same questions.

Over MCP

Plain HTTP API

For scripts and tools without MCP: send a question over HTTP and read the entry back as JSON.

Over HTTP

Let your agents ask first.

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.