sumo-mcp-readonly
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log verbosity (debug, info, warn, error) | info |
| SUMO_ACCESS_ID | Yes | Sumo Logic Access ID | |
| SUMO_ACCESS_KEY | Yes | Sumo Logic Access Key | |
| SUMO_API_BASE_URL | Yes | Regional API endpoint (e.g., https://api.sumologic.com/api) | |
| SUMO_MAX_RESULT_COUNT | No | Maximum results returned per query | 1000 |
| SUMO_QUERY_TIMEOUT_SECONDS | No | Timeout waiting for search job completion | 120 |
| SUMO_DEFAULT_SOURCE_CATEGORY | No | Default _sourceCategory for opinionated tools | |
| SUMO_MAX_QUERY_RANGE_MINUTES | No | Maximum allowed query time range in minutes | 1440 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sumo_search_logsA | Run a Sumo Logic log query. Provide either startTime+endTime or lastMinutes, but not both. Defaults to the last 15 minutes. |
| sumo_find_errorsA | Search for recent errors using an opinionated query that looks for ERROR, exception, failure, fatal, and stack traces. |
| sumo_search_correlation_idA | Search for a trace ID, request ID, correlation ID, transaction ID, or similar identifier across logs. The ID is safely escaped as a literal search term. |
| sumo_get_search_statusA | Get the current status of a Sumo Logic search job started by this MCP server process. |
| sumo_cancel_searchA | Cancel a running Sumo Logic search job started by this MCP server process. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools have mostly distinct purposes: general search, specialized error search, correlation ID search, status check, and cancel. The two specialized searches could be seen as overlapping with the general search, but their specific intents and query behavior are clearly described.
All tools share the 'sumo_' prefix and follow a verb_noun pattern. However, 'sumo_find_errors' uses 'find' instead of 'search', which is a minor deviation from the otherwise consistent use of 'search', 'get', and 'cancel'.
Five tools is well-scoped for a read-only Sumo Logic MCP server. Each tool addresses a distinct need: running searches, managing search jobs, and specialized search shortcuts, without unnecessary bloat.
The presence of search, status, and cancel suggests an asynchronous search job lifecycle, but there is no explicit tool to retrieve the actual results of a completed search. This is a notable gap that agents will need to work around, possibly expecting search_logs to return results synchronously, but this is not clearly indicated.