sumo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUMO_ENDPOINT | Yes | Sumo Logic API endpoint, e.g. https://api.us2.sumologic.com | |
| SUMO_ACCESS_ID | Yes | Your Sumo Logic access ID | |
| SUMO_ACCESS_KEY | Yes | Your Sumo Logic access key |
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 |
|---|---|
| search_logsA | Run a Sumo Logic search and return matching log lines. Use this to investigate production issues, find errors, trace events, or look up activity in logs. Returns trimmed messages with timestamp, source category, host, source name, and raw log line. |
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 1 tool
With only one tool, there is no potential for ambiguity. The single tool is clearly defined and cannot be confused with any other.
The single tool name 'search_logs' follows a clear verb_noun pattern, which is consistent and predictable.
A single tool for a logging platform seems insufficient. Typical users would expect additional tools for managing searches, retrieving past results, or listing sources, making the count feel too limited for the domain.
The server only offers a search functionality without supporting operations like listing saved searches, polling search status, or retrieving historical results. This leaves significant gaps for a complete log investigation workflow.