sumologic_mcp

The Sumologic MCP Python Server implements the MCP interface to expose Sumo Logic REST APIs through the MCP protocol. It provides tooling to perform log searches (with flexible query params, status monitoring, and paginated results), manage dashboards (list, create, update, delete, and retrieve configurations), query time-series metrics (with selectors and aggregations), manage collectors and their data sources, and handle monitoring rules (create, update, delete, enable/disable, and view execution history). Clients speaking MCP can connect to this server to drive these operations in a standardized way. To use it, install the Python package sumologic-mcp-python and run the server via the MCP runtime, then connect your MCP client to the server’s endpoint to issue CRUD and query operations across Sumo Logic resources.

Typical workflows include starting a server instance, authenticating with your Sumo Logic credentials, and issuing MCP requests to search logs, fetch dashboard metadata, retrieve metric data, or manage monitors and collectors. The server handles input validation and returns structured results suitable for client synchronization and state management.

Prerequisites:

• Python 3.8 or higher
• pip installed
• Access to a Sumo Logic account with API credentials (Access ID and Access Key)

Installation from PyPI:

pip install sumologic-mcp-python

Installation from Source:

# Clone the repository
git clone https://github.com/sumologic/sumologic-mcp-python.git
cd sumologic-mcp-python

# Install in editable mode (recommended for development)
pip install -e .

Development Installation (all extras):

pip install -e ".[dev]"

Configuration (choose one or more methods):

• Environment variables (SUMOLOGIC_ACCESS_ID, SUMOLOGIC_ACCESS_KEY, SUMOLOGIC_ENDPOINT, etc.)
• Configuration file (config.json) in JSON format (see README examples in the repository)
• Command-line options to override defaults

Starting the server (example):

sumologic-mcp-server

Or with explicit Python entry if using uvx: see mcp_config for details.

Tips and common considerations:

• Ensure your SUMOLOGIC_ACCESS_ID and SUMOLOGIC_ACCESS_KEY are kept secure and not checked into version control.
• The server supports multiple configuration sources with precedence: command-line arguments > environment variables > config file > defaults.
• For production, consider setting SUMOLOGIC_TIMEOUT and SUMOLOGIC_MAX_RETRIES to appropriate values for reliability.
• Validate configuration before starting the server with --validate-config to catch misconfigurations early.
• If using a configuration file, ensure valid JSON syntax and consult the example snippets in the README for required fields (access_id, access_key, endpoint).
• When using the MCP protocol, you can batch requests for dashboards, monitors, and searches to optimize client-server interactions.
• Logs may be controlled via SUMOLOGIC_LOG_LEVEL and SUMOLOGIC_LOG_FORMAT; adjust these for debugging or production-readiness.