Remote Filesystem MCP server
{
"mcpServers": {
"pulsemcp-remote-filesystem": {
"command": "npx",
"args": [
"-y",
"remote-filesystem-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-remote-filesystem": {
"command": "npx",
"args": [
"-y",
"remote-filesystem-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-remote-filesystem": {
"command": "npx",
"args": [
"-y",
"remote-filesystem-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"servers": {
"pulsemcp-remote-filesystem": {
"command": "npx",
"args": [
"-y",
"remote-filesystem-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "${input:agent_orchestrator_base_url}",
"FLY_IO_API_TOKEN": "${input:fly_io_api_token}"
}
}
},
"inputs": [
{
"id": "agent_orchestrator_base_url",
"type": "promptString",
"description": "Agent orchestrator base url",
"password": true
},
{
"id": "fly_io_api_token",
"type": "promptString",
"description": "Fly io api token",
"password": true
}
]
}{
"mcpServers": {
"pulsemcp-remote-filesystem": {
"command": "npx",
"args": [
"-y",
"remote-filesystem-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y remote-filesystem-mcp-serverversion 0.1.5
What it does
This MCP server provides tools for performing filesystem operations on Google Cloud Storage. It enables LLM-powered clients to read, write, list, and manage files stored in GCS buckets.
- List and browse the contents of GCS buckets to understand available files and directory structure.
- Read files from GCS into an LLM context for analysis or processing.
- Write or upload files to GCS buckets as part of automated workflows.
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.