Filelayer MCP Server

What this does

Filelayer exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

DATABASE_URL
FILELAYER_AS
FILELAYER_ORG
FILELAYER_DATA_DIR
S3_ENDPOINT
S3_BUCKET
S3_REGION
S3_ACCESS_KEY_ID
S3_SECRET_ACCESS_KEY
FILELAYER_MCP_AGENT_LABEL
FILELAYER_MCP_ALLOW_DESTRUCTIVE
FILELAYER_MCP_EXPOSE_AUDIT
FILELAYER_MCP_RETURN_BYTES
FILELAYER_BASE_URL

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Filelayer?

Run the Claude Code command in the install section to add Filelayer to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Filelayer?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Filelayer as well.

Does Filelayer need an API key?

Yes. Before it can run, set these environment variables: DATABASE_URL, FILELAYER_AS, FILELAYER_ORG, FILELAYER_DATA_DIR, S3_ENDPOINT, S3_BUCKET, S3_REGION, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY, FILELAYER_MCP_AGENT_LABEL, FILELAYER_MCP_ALLOW_DESTRUCTIVE, FILELAYER_MCP_EXPOSE_AUDIT, FILELAYER_MCP_RETURN_BYTES, FILELAYER_BASE_URL. They go in the env block of your MCP config.