Ext Ops Panel
Open dashboard
Comparison

Brandfolder MCP Server and API by Cotlet vs Keepsake

Brandfolder MCP Server and API by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Keepsake is an MCP server published by nicolascroce. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceBrandfolder MCP Server and API by CotletKeepsake
Official MCP Registry Listed
Version: 1.0.2
No figure published
Not marked · First seen
Listed
Version: 1.18.0
Downloads/month (npm): 1 644
Downloads/week (npm): 333
Forks (GitHub): 2
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.18.0
Downloads/month (npm): 1 644
Downloads/week (npm): 333
Forks (GitHub): 2
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Brandfolder MCP Server and API by Cotlet vs Keepsake
FactBrandfolder MCP Server and API by CotletKeepsake
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub2
Last release (differs)2026-11-10 (better)2026-11-04 (worse)
Where it runs (differs)Remote server (cotlet.dev/mcp/v1/brandfolder/connect)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/nicolascroce/keepsake-mcp
Changes in the last 7 days (differs)70
First seen (differs)2026-11-092026-10-11
Endpoint at the last check (differs)Answered with HTTP 302 (23 h ago)Responded 21 h ago, requires authentication

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Brandfolder MCP Server and API by Cotlet

In its own words, on Official MCP Registry:

Brandfolder digital asset management MCP server: search assets, get asset, add asset from URL.

Keepsake

In its own words, on Official MCP Registry:

Keepsake (keepsake.place), the app where creators and solo entrepreneurs empty their heads

How to run each

Brandfolder MCP Server and API by Cotlet As a remote MCP server

Claude Code
claude mcp add --transport http brandfolder https://cotlet.dev/mcp/v1/brandfolder/connect

Keepsake As a remote MCP server

Claude Code
claude mcp add --transport http keepsake https://app.keepsake.place/api/mcp

Requires: KEEPSAKE_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of Keepsake responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Brandfolder MCP Server and API by Cotlet publish no settings it asks for, so we do not compare settings.

What it can do: Brandfolder MCP Server and API by Cotlet · What it can do: Keepsake · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built