Clipps for Obsidian: your library, in your vault

Install

Three ways to install

The Community Plugins listing is where the plugin will live for the long term. BRAT is the fast lane while review is pending.

Community Plugins Coming soon

Obsidian → Settings → Community plugins

Open Obsidian and go to Settings
Open Community plugins and click Browse
Search for Clipps
Click Install, then Enable

Pending review by the Obsidian team. In the meantime, install via BRAT (below).

Via BRAT Available now

Beta Reviewer's Auto-update Tool

In Obsidian, open Settings → Community plugins → Browse
Search for BRAT, install and enable it
Open BRAT settings → Add Beta plugin
Paste the repo path below and confirm

Mkwell/obsidian-clipps

BRAT pulls new releases automatically as they land on GitHub.

Manual install

<your-vault>/.obsidian/plugins/clipps/

Grab main.js, manifest.json, and versions.json from the latest GitHub release
Drop them into the path below (create the clipps folder if it doesn't exist)
Restart Obsidian → Settings → Community plugins → enable Clipps

<your-vault>/.obsidian/plugins/clipps/
├── main.js
├── manifest.json
└── versions.json

For power users. Manual installs don't update on their own, so pull new releases yourself.

Setup

Three steps to first sync

After enabling the plugin, point it at your Clipps account and run the sync.

1

Open the plugin settings

In Obsidian, go to Settings → Clipps. You'll see fields for API key, target folder, and a sync button.

2

Authenticate

Pick whichever is easier:

Auto detect. If you've already run clipps login via the Clipps CLI, the plugin reads ~/.config/clipps/auth.json for you on desktop. Click Reload from auth.json in plugin settings.
Paste an API key. Generate one at app.clippsapp.com → Settings → Developer, then paste it into the plugin.

3

Run the sync

Open the command palette (Cmd+P / Ctrl+P) and run the command below, or click the Clipps ribbon icon in the left sidebar. To sync just one Brain, list, or content type instead, run the matching scoped command.

Clipps: Sync from Clipps
Clipps: Sync a brain
Clipps: Sync a list
Clipps: Sync a content type

What you get

What gets synced

Every save in your Clipps library becomes one markdown file with rich frontmatter and a body that knows which module fired.

One file per save Every video, article, recipe, and note becomes a single markdown document in your target folder.
Rich frontmatter Source URL, platform, topics, content type, dates, and the fields each module exposes, all queryable by Dataview.
Body shaped by module Books, movies, TV, anime, manga, music, recipes, and sneakers each render with cover art at the top, then the right links (Where to Watch, Buy, Read, Listen, Retailers), then references like Goodreads, IMDB, MAL.
Four sync scopes Sync the full library, one Brain, one list, or one content type. Each is its own command in the palette.
Save URLs from any note Highlight a URL anywhere in your vault and run Clipps: Save this URL. It hits the Clipps API and the new entry shows up on the next sync.
Search the live library Clipps: Search library opens a modal that queries Clipps in real time. Click a hit to jump to the local synced note, or get prompted to sync it if you haven't yet.
Chat with any Brain Clipps: Ask my brain... picks a Brain and opens a chat that holds context across turns. Citations come back as wikilinks straight to the local notes.
Module tags and MOC notes Every saved item gets clipps/module/<slug> tags. The plugin writes Map-of-Content notes at <your folder>/Modules/Books.md, Movies.md, and so on, each with a Dataview block that lists every entry of that type.
Mirror media into the vault A toggle in settings decides whether thumbnails and original media files download into your vault or stay as remote links. Off by default on mobile.
Schema versioning, safe rewrites Running sync again only rewrites notes where Clipps has fresher data, or where the note's schema is older than the current plugin. Manual edits in Obsidian persist.

---
title: "15-Minute Crispy Chickpea Bowls"
source: https://www.tiktok.com/@anna/video/7299...
platform: tiktok
module: recipe
topics: ["vegetarian", "weeknight", "chickpeas"]
servings: 2
created: 2026-04-11T18:42:00Z
updated: 2026-04-22T09:15:00Z
---

# 15-Minute Crispy Chickpea Bowls

![thumbnail](https://cdn.clippsapp.com/v/abc123/thumb.jpg)

## Summary
Sheet-pan chickpeas with smoked paprika, served over greens with
a tahini-lemon dressing. Caption notes a 425°F oven, 18 minutes.

## Ingredients
- 1 can chickpeas, drained and patted dry
- 2 tbsp olive oil
- 1 tsp smoked paprika
- 1/2 tsp cumin
- Kosher salt
- 3 tbsp tahini
- 1 lemon, juiced
- 2 cups arugula or baby spinach

## Notes
Pat the chickpeas REALLY dry. The whole thing only crisps if
they start dry.

## Source
- [Open on TikTok](https://www.tiktok.com/@anna/video/7299...)
- [View in Clipps](https://app.clippsapp.com/v/abc123)

Compose

Once it's in your vault

This is where Obsidian shines. Treat your Clipps library like any other set of notes you'd link, query, and pull into your daily flow.

Wikilink to videos from your daily notes: Watched [[that-claude-code-video]] today
Use Dataview queries: LIST FROM "Clipps" WHERE platform = "youtube" SORT created DESC
Click any clipps/module/<slug> tag in a note's properties pane to surface every saved item of that type
Open the MOC notes the plugin writes under Modules/ for a Dataview index of every Book, Movie, Recipe, Sneaker, and so on
Search across transcripts, summaries, and your own notes with Obsidian's built in search
Pair with the Clipps MCP so your AI assistant can query your vault and your live library together

FAQ

Questions, answered

Where is the data stored?

Your vault is local files on your machine. The plugin pulls from Clipps's API and writes markdown into the folder you configure. Clipps still hosts the original media; the markdown is a text projection of your library.

Does sync overwrite my edits?

No. The plugin checks updatedAt on each item against your file's frontmatter. If your file is newer or unchanged, it skips. Only files where Clipps has fresher data get rewritten. Manual edits you add in Obsidian merge cleanly on the next sync.

Mobile?

Obsidian on iOS and Android works, but the plugin can only read ~/.config/clipps/auth.json automatically on desktop (no filesystem access on mobile). On mobile, paste an API key manually in the plugin settings.

Storage cost?

A 680-video library is roughly 5-15 MB of markdown depending on transcript length. Negligible against a typical vault.

Can I sync only specific brains or lists?

Yes. There are four sync scopes, each with its own command: Sync from Clipps (full library), Sync a brain, Sync a list, Sync a content type. Scoped syncs land in their own subfolder under your Clipps folder so you can keep, say, a Cooking Brain isolated from the rest.

What's the difference between this and the Clipps MCP?

The plugin writes static markdown into your vault for you to read, link, and search. The MCP is a live API for your AI assistant. They compose: install both, your AI queries Clipps live and reads your vault notes.

Do I need a paid Clipps account?

No. The plugin works with any Clipps account. Free tier limits apply where they apply in the app.

Your library,in your vault.