remote-filesystem MCP Server

What this does

remote-filesystem 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:

GCS_BUCKET
GCS_PROJECT_ID
GCS_CLIENT_EMAIL
GCS_PRIVATE_KEY
GOOGLE_APPLICATION_CREDENTIALS
GCS_ROOT_PATH
GCS_MAKE_PUBLIC
ENABLED_TOOLGROUPS

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

How do I install remote-filesystem?

Run the Claude Code command in the install section to add remote-filesystem 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 remote-filesystem?

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 remote-filesystem as well.

Does remote-filesystem need an API key?

Yes. Before it can run, set these environment variables: GCS_BUCKET, GCS_PROJECT_ID, GCS_CLIENT_EMAIL, GCS_PRIVATE_KEY, GOOGLE_APPLICATION_CREDENTIALS, GCS_ROOT_PATH, GCS_MAKE_PUBLIC, ENABLED_TOOLGROUPS. They go in the env block of your MCP config.