Ext Ops Panel
Open dashboard
Comparison

filestack-claude-plugin vs Filelayer

filestack-claude-plugin is a plugin bundle for AI coding tools published by filestack. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Filelayer is an MCP server published by filelayer.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacefilestack-claude-pluginFilelayer
Claude Code: claude-plugins-community Listed
Version: 1.3.0
Forks (GitHub): 4
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.32.0
Downloads/month (npm): 5 676
Downloads/week (npm): 2 798
Forks (GitHub): 0
Stars (GitHub): 0
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

filestack-claude-plugin vs Filelayer
Factfilestack-claude-pluginFilelayer
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)0 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleOn your machine (@filelayer/core)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 214, secrets among them: 3
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/filestack/filestack-claude-plugingithub.com/filelayer/filelayer
Changes in the last 7 days (differs)06
First seen2026-10-112026-10-11

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

filestack-claude-plugin

In its own words, on Claude Code: claude-plugins-community:

Filestack is a file handling platform-as-a-service used by thousands of applications for uploads, cloud source ingestion (Google Drive, Dropbox, Instagram, and 14 more), on-the-fly image/video/document processing via CDN, and policy-based security. This plugin brings the full Filestack platform into Claude Code through 10 MCP tools (upload, retrieve, delete, store URL, build and apply CDN transformations, list available transforms, generate security policies, sign policies, generate signed URLs), 3 context-aware skills (SDK integration guidance, API error diagnosis, and webhook signature verification setup), and a natural language /filestack-transform slash command that converts plain English into Filestack CDN transformation URLs.

Filelayer

In its own words, on Official MCP Registry:

User files for a SaaS, under one person's authority: list, share with an expiry, revoke.

How to run each

filestack-claude-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install filestack-claude-plugin@claude-community

Filelayer As a local MCP server: npm package

Claude Code
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --env "FILELAYER_AS=<YOUR_FILELAYER_AS>" --env "FILELAYER_ORG=<YOUR_FILELAYER_ORG>" --env "S3_ACCESS_KEY_ID=<YOUR_S3_ACCESS_KEY_ID>" --env "S3_SECRET_ACCESS_KEY=<YOUR_S3_SECRET_ACCESS_KEY>" --transport stdio core -- npx -y @filelayer/core -p @filelayer/core filelayer-mcp

Requires: DATABASE_URL (secret), FILELAYER_AS, FILELAYER_ORG, S3_ACCESS_KEY_ID (secret), S3_SECRET_ACCESS_KEY (secret)

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

Tools each declares

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

Settings each asks for

Only filestack-claude-plugin asks for

  • FILESTACK_API_KEY (secret)
  • FILESTACK_APP_SECRET (secret)

Only Filelayer asks for

  • DATABASE_URL (secret)
  • FILELAYER_AS
  • FILELAYER_BASE_URL
  • FILELAYER_DATA_DIR
  • FILELAYER_MCP_AGENT_LABEL
  • FILELAYER_MCP_ALLOW_DESTRUCTIVE
  • FILELAYER_MCP_EXPOSE_AUDIT
  • FILELAYER_MCP_RETURN_BYTES
  • FILELAYER_ORG
  • S3_ACCESS_KEY_ID (secret)
  • S3_BUCKET
  • S3_ENDPOINT
Show the remaining 2
  • S3_REGION
  • S3_SECRET_ACCESS_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: filestack-claude-plugin · What it can do: Filelayer · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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