File Store MCP Server

If you already use File Store, the file store mcp server is the piece that lets your assistant work with it directly. file store mcp server.

What the server does

A file storage service supporting multiple cloud providers

• Multi-cloud storage provider support
• Unified API for file uploads
• Presigned URL generation for secure access
• Support for AWS S3, Alibaba Cloud OSS, Tencent Cloud COS, Qiniu Cloud, and GitHub
• Easy configuration via environment variables
• Customizable URL expiration times

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Installation — The Installation tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: FSM_S3_REGION, FSM_S3_ACCESS_KEY, FSM_S3_SECRET_KEY, FSM_OSS_ACCESS_KEY, FSM_OSS_SECRET_KEY, FSM_COS_REGION, FSM_COS_APP_ID, FSM_COS_ACCESS_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. File Store's toolset — Installation — is a fair guide to whether it matches your workflow. It is maintained by sjzar; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against File Store's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.