sumo-logic-mcp
Provides 37 tools for interacting with Sumo Logic, enabling search and analytics, monitor management, alert management, dashboard management, collector and source management, and metrics queries.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@sumo-logic-mcplist all monitors with critical status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
sumo-logic-mcp
MCP server for Sumo Logic — 37 tools for searching logs, managing monitors, alerts, dashboards, collectors, and metrics.
Zero hardcoded org-specific values. Any team can plug in their own credentials and start querying immediately.
Quick Start
1. Install
pip install sumo-logic-mcp2. Get Sumo Logic Credentials
Generate an Access Key in the Sumo Logic UI: Preferences > Security > Access Keys.
You need:
Access ID — the key identifier
Access Key — the secret (shown only once at creation)
API Endpoint — depends on your deployment region (see table below)
3. Configure Your MCP Client
Add to your MCP client configuration (e.g., ~/.cursor/mcp.json or equivalent):
{
"mcpServers": {
"sumologic": {
"command": "python3",
"args": ["-m", "sumo_logic_mcp"],
"env": {
"SUMOLOGIC_ACCESS_ID": "<your-access-id>",
"SUMOLOGIC_ACCESS_KEY": "<your-access-key>",
"SUMOLOGIC_ENDPOINT": "https://api.sumologic.com"
}
}
}
}Or run directly:
export SUMOLOGIC_ACCESS_ID="your-access-id"
export SUMOLOGIC_ACCESS_KEY="your-access-key"
export SUMOLOGIC_ENDPOINT="https://api.sumologic.com"
python3 -m sumo_logic_mcpRelated MCP server: Overwatch MCP
API Endpoints by Region
Deployment | API Endpoint |
US1 |
|
US2 |
|
EU |
|
AU |
|
CA |
|
DE |
|
IN |
|
JP |
|
KR |
|
FED |
|
Determine yours from your Sumo Logic login URL (e.g., service.us2.sumologic.com → US2).
Tool Reference
Search & Analytics (4 tools)
Tool | Description | Required Params |
| Execute a log search (full lifecycle: create job → poll → fetch → cleanup) |
|
| Check status of a running search job |
|
| Fetch messages or records from a search job |
|
| Cancel a running search job |
|
search_logs optional params: from_time (default -15m), to_time (default now), timezone (default UTC), limit (default 100), by_receipt_time, timeout (default 300s).
Time formats: ISO 8601 (2024-01-15T09:00:00), relative (-15m, -1h, -2d, -1w), epoch ms (1718745600000), or now.
Monitor Management (10 tools)
Tool | Description | Required Params |
| List all monitors | — |
| Search by name or status filter |
|
| Get full monitor configuration |
|
| Create a new monitor |
|
| Update monitor config (read-modify-write) |
|
| Delete a monitor (irreversible) |
|
| Enable a disabled monitor |
|
| Disable a monitor |
|
| Get current health/triggering state |
|
| Get alert history for a monitor |
|
Search filter examples: monitorStatus:Critical, monitorStatus:Warning, monitorStatus:AllTriggered.
Alert Management (3 tools)
Tool | Description | Required Params |
| Get all currently firing alerts | — |
| Get detailed alert info for a monitor |
|
| Resolve an alert by disabling its monitor |
|
Dashboard Management (5 tools)
Tool | Description | Required Params |
| List dashboards with pagination | — |
| Get full dashboard config |
|
| Create a dashboard with panels and layout |
|
| Update dashboard config (read-modify-write) |
|
| Delete a dashboard (irreversible) |
|
Collector & Source Management (8 tools)
Tool | Description | Required Params |
| List all collectors | — |
| Get collector configuration |
|
| Create a new Hosted collector |
|
| Update collector config (with ETag locking) |
|
| Delete a collector and its sources |
|
| List sources on a collector |
|
| Get source configuration |
|
| Create an HTTP source (returns endpoint URL) |
|
Metrics (4 tools)
Tool | Description | Required Params |
| Execute a metrics query |
|
| Discover available metric names | — |
| Get dimensions for a metric |
|
| List metric content types | — |
Utility (3 tools)
Tool | Description | Required Params |
| Verify API connectivity and auth | — |
| Get account status and ingestion info | — |
| Check if a query is syntactically valid |
|
Usage Examples
Once configured, just ask your AI assistant naturally:
"Search for 500 errors in the last hour"
→ AI calls search_logs with appropriate query
"Show me all critical alerts"
→ AI calls get_active_alerts with status=Critical
"Create a monitor for high error rates on our API"
→ AI calls create_monitor with query, threshold, and notification params
"List all hosted collectors"
→ AI calls list_collectors with filter_type=hosted
"What CPU metrics are available?"
→ AI calls list_metric_definitionsDevelopment
git clone https://github.com/rajfirke/sumo-logic-mcp.git
cd sumo-logic-mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
# Lint
ruff check src/ tests/
# Test
pytest -v
# Run locally
export SUMOLOGIC_ACCESS_ID="..."
export SUMOLOGIC_ACCESS_KEY="..."
export SUMOLOGIC_ENDPOINT="https://api.sumologic.com"
python3 -m sumo_logic_mcpArchitecture
src/sumo_logic_mcp/
├── __init__.py # Exports mcp, triggers tool registration
├── __main__.py # Entry point: python -m sumo_logic_mcp
├── server.py # FastMCP instance + lifespan (shared HTTP client)
├── client.py # Async HTTP client (httpx, Basic Auth, retry, cookies)
├── validation.py # Time parsing and validation
└── tools/
├── __init__.py # Imports all tool modules
├── search.py # 4 search tools
├── monitors.py # 10 monitor tools
├── alerts.py # 3 alert tools
├── dashboards.py # 5 dashboard tools
├── collectors.py # 8 collector/source tools
├── metrics.py # 4 metrics tools
└── utils.py # 3 utility toolsDesign Decisions
Zero org-specific config — Only 3 env vars needed: access ID, access key, endpoint. No hardcoded indexes, source categories, or query patterns.
Cookie persistence — httpx's built-in cookie jar handles Sumo's session routing (requests without cookies get 404/500).
Timezone passed through — The
timeZoneparameter is always sent to the API, defaulting to UTC. The reference implementation silently dropped it.NOT STARTED is valid — Sumo's search API returns "NOT STARTED" as an initial state. We treat it as an intermediate polling state (the reference treated it as fatal).
Job cleanup — Search jobs are always deleted in a
finallyblock after fetching results.ETag locking — Collector updates use
If-Matchheaders for optimistic concurrency control.Aware datetimes only — All time operations use
datetime.now(timezone.utc), never the deprecateddatetime.utcnow().
License
Apache 2.0 — see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rajfirke/sumo-logic-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server