Filelayer MCP Server

by filelayerdev.filelayer/corev0.33.0

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

0Node.jsstdioofficial registry

context tax

pending

security

pending

cold start

pending

freshness

pending

Our reading of Filelayer, from the data

Filelayer is an MCP server from filelayer, listed in the official MCP Registry.

We haven't measured its tool list yet, so its token cost is unknown.

It runs locally on your machine over stdio and needs 3 secrets (DATABASE_URL, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY); use a scoped, least-privilege key.

Install Filelayer MCP server

claude mcp add core-filelayer -e DATABASE_URL='<database-url>' -e FILELAYER_AS='<filelayer-as>' -e FILELAYER_ORG='<filelayer-org>' -e S3_ACCESS_KEY_ID='<s3-access-key-id>' -e S3_SECRET_ACCESS_KEY='<s3-secret-access-key>' -- npx -y @filelayer/core -p @filelayer/core filelayer-mcp

{
  "mcpServers": {
    "core-filelayer": {
      "command": "npx",
      "args": [
        "-y",
        "@filelayer/core",
        "-p",
        "@filelayer/core",
        "filelayer-mcp"
      ],
      "env": {
        "DATABASE_URL": "<database-url>",
        "FILELAYER_AS": "<filelayer-as>",
        "FILELAYER_ORG": "<filelayer-org>",
        "S3_ACCESS_KEY_ID": "<s3-access-key-id>",
        "S3_SECRET_ACCESS_KEY": "<s3-secret-access-key>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

{
  "mcpServers": {
    "core-filelayer": {
      "command": "npx",
      "args": [
        "-y",
        "@filelayer/core",
        "-p",
        "@filelayer/core",
        "filelayer-mcp"
      ],
      "env": {
        "DATABASE_URL": "<database-url>",
        "FILELAYER_AS": "<filelayer-as>",
        "FILELAYER_ORG": "<filelayer-org>",
        "S3_ACCESS_KEY_ID": "<s3-access-key-id>",
        "S3_SECRET_ACCESS_KEY": "<s3-secret-access-key>"
      }
    }
  }
}

Settings → Developer → Edit Config (claude_desktop_config.json), then restart.

{
  "servers": {
    "core-filelayer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@filelayer/core",
        "-p",
        "@filelayer/core",
        "filelayer-mcp"
      ],
      "env": {
        "DATABASE_URL": "<database-url>",
        "FILELAYER_AS": "<filelayer-as>",
        "FILELAYER_ORG": "<filelayer-org>",
        "S3_ACCESS_KEY_ID": "<s3-access-key-id>",
        "S3_SECRET_ACCESS_KEY": "<s3-secret-access-key>"
      }
    }
  }
}

Add to .vscode/mcp.json in your workspace.

{
  "mcpServers": {
    "core-filelayer": {
      "command": "npx",
      "args": [
        "-y",
        "@filelayer/core",
        "-p",
        "@filelayer/core",
        "filelayer-mcp"
      ],
      "env": {
        "DATABASE_URL": "<database-url>",
        "FILELAYER_AS": "<filelayer-as>",
        "FILELAYER_ORG": "<filelayer-org>",
        "S3_ACCESS_KEY_ID": "<s3-access-key-id>",
        "S3_SECRET_ACCESS_KEY": "<s3-secret-access-key>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json.

Configuration

Variable	Required	Secret	Description
DATABASE_URL	yes	yes	Your own PostgreSQL, where this library keeps file ownership, grants and the audit chain. Apply node_modules/@filelayer/core/schema.sql once before starting.
FILELAYER_AS	yes	—	The ONE subject this server speaks for, in your own id space. Fixed for the life of the process: no tool reads it as an argument and no tool can change it, which is the only reason exposing these tools to an agent is safe. Write it yourself or have your provisioning write it, never derive it from a conversation. Serving several people means starting several servers.
FILELAYER_ORG	yes	—	The organisation this server is scoped to, in your own id space.
FILELAYER_DATA_DIR	—	—	A local directory for the bytes. Needs no bucket and no IAM user. Set this OR the S3_* block: with neither, the server refuses to start rather than falling back to memory, which would work in a demo and lose the first real file.
S3_ENDPOINT	—	—	An S3-compatible endpoint, for example https://<account>.r2.cloudflarestorage.com. Setting it makes S3_BUCKET, S3_ACCESS_KEY_ID and S3_SECRET_ACCESS_KEY required.
S3_BUCKET	—	—	The bucket. It must be private: this library decides who may be GIVEN a URL and has no say in who the object store will answer. `npx -p @filelayer/core filelayer doctor` reports whether yours serves unauthenticated reads.
S3_REGION	—	—	Region, or `auto` for Cloudflare R2.
S3_ACCESS_KEY_ID	—	yes	Access key id for the bucket.
S3_SECRET_ACCESS_KEY	—	yes	Secret access key for the bucket.
FILELAYER_MCP_AGENT_LABEL	—	—	How this agent names itself in the audit trail, recorded on every event these tools produce. It is what lets the chain separate "the partner opened this document" from "the partner's assistant opened this document".
FILELAYER_MCP_ALLOW_DESTRUCTIVE	—	—	Set to exactly `true` to register delete_file. Off by default because deleting is not recoverable and an agent that misreads a sentence deletes the wrong thing silently.
FILELAYER_MCP_EXPOSE_AUDIT	—	—	Set to exactly `true` to register file_audit. Off by default because the trail is an organisation's whole history and a tool that returns it copies every file name, actor and denial into the model's context. Reading it is itself audited since 0.27.0, which was the previous reason; the default did not move.
FILELAYER_MCP_RETURN_BYTES	—	—	Set to exactly `true` to register read_file. Off by default because a document returned by a tool is a document copied into a model's context; file_info plus a share link is usually what was actually needed.
FILELAYER_BASE_URL	—	—	The base of the share URLs this instance mints. Without it, share links come back without a URL.

Freshness

Not enough public signals yet to judge maintenance.

Last commit (default branch)
2026-10-18 · today · GitHub
Latest release
no data · GitHub
Package published
no data · npm/PyPI
Registry entry updated
2026-10-16 · 3d ago · official registry · v0.33.0

FAQ

›How do I install the Filelayer MCP server in Claude Code?

Run: claude mcp add core-filelayer -e DATABASE_URL='<database-url>' -e FILELAYER_AS='<filelayer-as>' -e FILELAYER_ORG='<filelayer-org>' -e S3_ACCESS_KEY_ID='<s3-access-key-id>' -e S3_SECRET_ACCESS_KEY='<s3-secret-access-key>' -- npx -y @filelayer/core -p @filelayer/core filelayer-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Filelayer require an API key?

Yes. It expects DATABASE_URL, FILELAYER_AS, FILELAYER_ORG, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY, of which 3 are secrets.

›Can I use Filelayer as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Filelayer in the official MCP registry?

Yes, as dev.filelayer/core.

Sources and method

Official MCP Registry entry: updated 2026-10-16
GitHub repository: fetched 2026-10-19
Package registry (npm / PyPI): listed
Last checked against all sources: 2026-10-19

The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Spot an error? Request a correction or claim the listing.

Our reading of Filelayer, from the data

Install Filelayer MCP server

Install in Claude Code

Install in Cursor

Install in Claude Desktop

Install in VS Code

Install in Windsurf

Configuration

Freshness

FAQ

Sources and method