Gcs MCP server
{
"mcpServers": {
"pulsemcp-gcs": {
"command": "npx",
"args": [
"-y",
"gcs-google-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-gcs": {
"command": "npx",
"args": [
"-y",
"gcs-google-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-gcs": {
"command": "npx",
"args": [
"-y",
"gcs-google-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"servers": {
"pulsemcp-gcs": {
"command": "npx",
"args": [
"-y",
"gcs-google-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-gcs": {
"command": "npx",
"args": [
"-y",
"gcs-google-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 gcs-google-mcp-serverversion 0.1.14
What it does
MCP server that provides access to Google Cloud Storage with fine-grained tool-level access control. Allows LLM-powered clients to interact with GCS buckets and objects through controlled tool operations.
- Upload, download, or list objects in GCS buckets from an LLM application.
- Grant selective access to specific GCS operations based on user roles or application requirements.
- Integrate GCS file operations into agentic workflows with controlled permissions.
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.