Cloud Tasks

MCP Server to interact with Google Cloud Tasks

javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "gitskyflux-cloudtasks-mcp": {
      "command": "node",
      "args": [
        "/path/to/cloudtasks-mcp/build/index.js"
      ],
      "env": {
        "GOOGLE_CLOUD_LOCATION_PROJECTS": "location:project-id"
      }
    }
  }
}

You can run a Cloud Tasks MCP Server to interact with Google Cloud Tasks queues and tasks from your MCP client. It exposes tools to list queues and tasks, get details, pause/resume queues, and delete tasks, making it easy to manage Cloud Tasks from your MCP setup.

How to use

Use the Cloud Tasks MCP Server from your MCP client to perform common Cloud Tasks operations. You can list queues in a specific location, inspect a queue or task in detail, pause or resume queues, list tasks within a queue, and delete tasks. Each action is exposed as a tooling endpoint you invoke through your MCP client to manage Cloud Tasks programmatically.

How to install

Prerequisites you need before installing: Node.js and npm are installed on your system.

Install via Smithery (automatic for Claude Desktop):

npx -y @smithery/cli install @gitskyflux/cloudtasks-mcp --client claude

Manual installation

Step 1. Install dependencies

npm install

Step 2. Build the project

npm run build

Step 3. Configure Claude Desktop to run the MCP server

"cloudtasks-mcp": {
  "command": "node",
  "args": [
    "/path/to/cloudtasks-mcp/build/index.js"
  ],
  "env": {
    "GOOGLE_CLOUD_LOCATION_PROJECTS": "location:project-id"
  }
}

Notes on configuration

Replace the path in args with the actual path to index.js. Define a comma-separated list of location:project-id pairs in GOOGLE_CLOUD_LOCATION_PROJECTS, where the first listed project is the default. Example: us-east1:google-project-id1,us-central1:google-project-id2.

The application expects to find JSON credential files in a keys folder for each project, e.g. keys/google-project-id1.json. Ensure the relevant Cloud Tasks service account has appropriate permissions (e.g., Cloud Tasks Admin or a suitable subset).

Available tools

listQueues

List all Cloud Tasks queues in a specified location.

getQueue

Get details of a specific Cloud Tasks queue.

pauseQueue

Pause a Cloud Tasks queue.

resumeQueue

Resume a paused Cloud Tasks queue.

listTasks

List tasks in a Cloud Tasks queue.

getTask

Get details of a specific task in a Cloud Tasks queue.

deleteTask

Delete a task from a Cloud Tasks queue.