Filelayer MCP Server

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

Packages and local setup

The published npm package is @filelayer/core, version 0.30.0. Its declared MCP transport is stdio.

The package declares DATABASE_URL (required): 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 (required): 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 (required): 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:// .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: Access key id for the bucket.; S3_SECRET_ACCESS_KEY: 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..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.30.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.