home / mcp / cloud logging mcp server

Cloud Logging MCP Server

MCP Server generated by mcp.ag2.ai

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "ag2-mcp-servers-cloud-logging-api": {
      "command": "python",
      "args": [
        "mcp_server/main.py",
        "stdio"
      ],
      "env": {
        "CONFIG": "{...}",
        "SECURITY": "YOUR_API_KEYS_OR_SECRETS",
        "CONFIG_PATH": "path/to/mcp_config.json"
      }
    }
  }
}

This MCP server exposes the Google Cloud Logging API as an MCP endpoint, allowing clients to interact with the API through a lightweight, protocol-agnostic interface. It translates between MCP requests and the Google Logging API, enabling you to integrate logging data into your MCP-powered tooling and workflows.

How to use

Start the MCP server in stdio mode. This runs locally and connects to clients via standard input/output, making it easy to integrate with your existing tooling or test harnesses. Begin by launching the server, then connect your MCP client to the process input/output streams or to your orchestration layer that manages stdio MCP servers.

How to install

Prerequisites: Python 3.9 or later, pip, and uv (optional for alternative running). Ensure you have a working Python environment before installing.

# Step 1: Install dependencies
pip install -e ".[dev]"

# If you prefer to run with uv (optional):
uv pip install --editable ".[dev]"

Step 2: Run the server in stdio mode using the provided command. This starts the MCP server process and exposes an input/output interface for your MCP client.

python mcp_server/main.py stdio

Step 3: Configure the server using environment variables if needed. You can provide a JSON configuration or a path to your configuration file.

Additional configuration and security

Environment variables to configure the server include the path to a JSON configuration file, a JSON string containing the configuration, and security parameters such as API keys. These can be supplied at runtime to customize the MCP server behavior and access controls.

{
  "CONFIG_PATH": "path/to/mcp_config.json",
  "CONFIG": "{...}",
  "SECURITY": "YOUR_API_KEYS_OR_SECRETS"
}
```",

Notes on running modes and testing

The server supports multiple transport modes and can be exercised via your MCP client in a development or test environment. Use the stdio configuration when you want straightforward, in-process communication, or wire the server into a test harness that manages process I/O.