sumo-logic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUMOLOGIC_ENDPOINT | Yes | API endpoint for your Sumo Logic deployment region (e.g., https://api.sumologic.com) | https://api.sumologic.com |
| SUMOLOGIC_ACCESS_ID | Yes | Your Sumo Logic Access ID (key identifier) | |
| SUMOLOGIC_ACCESS_KEY | Yes | Your Sumo Logic Access Key (secret) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_usersA | List all users in the account. Returns user names, emails, role IDs, active status, and last login timestamps. Supports pagination via token. |
| list_rolesA | List all roles in the account (v2 API). Returns role names, capabilities, assigned users, and data access filters (log analytics, audit, security). |
| list_fieldsA | List all fields (built-in and custom). Returns field names, data types, and states. Useful for understanding what fields are available for searching and building field extraction rules. |
| list_field_extraction_rulesA | List field extraction rules (FERs). Returns rule names, scopes, parse expressions, enabled status, and extracted field names. FERs automatically parse fields from log messages at ingest time. |
| list_partitionsA | List all index partitions. Returns partition names, routing expressions, analytics tiers, retention periods, and whether they're included in default searches. Partitions control how data is indexed and retained. |
| list_lookup_tablesA | List all lookup tables. Returns table names, descriptions, field schemas, primary keys, TTL settings, and size limit actions. Lookup tables are used for enrichment in search queries via the 'lookup' operator. |
| get_lookup_tableA | Get a lookup table's configuration and schema. Returns the table's field definitions, primary keys, TTL, size limit action, and parent folder ID. |
| list_ingest_budgetsA | List all ingest budgets (v2). Returns budget names, scopes, capacity in bytes, timezone, reset time, and actions taken when capacity is exceeded. Ingest budgets control data volume limits per scope. |
| get_active_alertsA | Get all currently active/firing alerts. Returns monitors in a triggered state. Filter by severity using the status parameter: Critical, Warning, MissingData, or AllTriggered for all. |
| get_alert_detailsA | Get detailed information about an active alert. Returns the monitor's status, trigger conditions, queries, notification config, and playbook. |
| resolve_alertA | Resolve an active alert by disabling its monitor. Sumo Logic auto-resolves alerts when trigger conditions are no longer met. For manual resolution, this disables the monitor to stop the alert. Use enable_monitor to reactivate afterward. |
| list_collectorsB | List all collectors with their IDs, names, types, and status. |
| get_collectorA | Get a collector's full configuration and status. |
| create_hosted_collectorA | Create a new Hosted collector. Hosted collectors are cloud-managed and used for HTTP sources, cloud-to-cloud integrations, and AWS polling sources. Installed collectors cannot be created via API. |
| update_collectorA | Update a collector's configuration (read-modify-write). Fetches current config with ETag, merges your changes, and saves with optimistic locking. |
| delete_collectorA | Delete a collector and all its sources. WARNING: This action is irreversible. All sources on this collector will also be deleted. |
| list_sourcesA | List all sources configured on a collector. |
| get_sourceB | Get a source's full configuration. |
| create_http_sourceA | Create an HTTP source on a Hosted collector. Returns the source config including the unique HTTP endpoint URL where data can be sent via POST. |
| get_personal_folderA | Get the current user's personal content folder. Returns the root of your personal library including child items (saved searches, dashboards, folders). Use the returned ID as a starting point to navigate the content library. |
| get_folderA | Get a content folder and its children. Returns the folder metadata and a list of child items (searches, dashboards, sub-folders) with their IDs and types. |
| get_content_by_pathA | Look up a content item by its library path. Returns the item's ID, name, type, and parent info. Paths start with /Library/. |
| list_dashboardsA | List dashboards with pagination. Returns dashboard titles, IDs, and descriptions. Use the 'next' token from the response to fetch subsequent pages. |
| get_dashboardA | Get a dashboard's full configuration. Returns the complete definition including panels, layout, variables, time range, and visual settings. |
| create_dashboardA | Create a new dashboard with panels, layout, and variables. Panels use a 24-column grid layout. Each panel needs a unique 'key' that maps to a layoutStructures entry defining its grid position (x, y, width, height). Panel types: TextPanel (markdown text), SumoSearchPanel (log/ metric queries with charts), ServiceMapPanel, TracesListPanel. |
| update_dashboardA | Update a dashboard's configuration (read-modify-write). Fetches the current config, merges your changes, and saves. Pass a JSON object with only the fields you want to change. For panels/layout, pass the complete arrays. |
| delete_dashboardB | Delete a dashboard. WARNING: This action is irreversible. |
| query_metricsA | Execute a metrics query and return time-series data. Uses the same query syntax as the Sumo Logic UI. Supports operators like avg, sum, min, max, rate, delta, topk, outlier, predict, and grouping with 'by'. |
| list_metric_definitionsA | List available metric names. Discovers metrics by running a short-range query and extracting unique metric names from the results. Use filter_query to narrow by source category, content type, or other dimensions. |
| get_metric_metadataA | Get metadata (dimensions and their values) for a metric. Runs a short query for the named metric and extracts all dimension keys and sample values from the results. |
| list_metric_namespacesA | List metric namespaces (content types). Discovers available metric sources by querying for unique _contentType values (e.g. HostMetrics, AwsCloudWatch, MetricFromLog). These serve as logical namespaces. |
| list_monitorsB | List all monitors with their names, IDs, types, and statuses. |
| search_monitorsA | Search monitors by name, description, or status filter. Filter examples: monitorStatus:Critical, monitorStatus:Warning, monitorStatus:AllTriggered, type:MonitorsLibraryMonitor. |
| get_monitorA | Get a monitor's full configuration and current status. |
| create_monitorA | Create a new Sumo Logic monitor. For simple threshold monitors, use threshold/trigger_type params. For complex monitors (anomaly, outlier, multiple triggers, webhook notifications), pass triggers_json and/or notifications_json with the full JSON arrays. |
| update_monitorA | Update a monitor's configuration (read-modify-write). Fetches the current config, merges your changes, and saves. Pass a JSON object with only the fields you want to change. |
| delete_monitorA | Delete a monitor and all its associated alerts. WARNING: This action is irreversible. |
| enable_monitorA | Enable a disabled monitor so it resumes evaluating. |
| disable_monitorA | Disable a monitor to stop evaluation and alerting. |
| get_monitor_statusA | Get the current health and triggering state of a monitor. Returns whether the monitor is Normal, Critical, Warning, MissingData, or Disabled. |
| get_monitor_historyA | Get alert/trigger history for a monitor. Returns events within the time range. Falls back to current status if the history endpoint is unavailable. |
| search_logsA | Execute a Sumo Logic log search and return results. Handles the full search lifecycle: creates a job, polls until done, fetches results, and cleans up. For aggregation queries (containing count, sum, avg, group by, etc.) returns aggregated records. For raw queries returns log messages. |
| get_search_statusA | Check the status of a running or completed search job. Returns the current state, message count, record count, and any pending warnings or errors since the last status check. |
| get_search_resultsA | Fetch results from a search job. Use 'messages' for raw log lines. Use 'records' for aggregated results (queries with count, sum, avg, group by, etc.). Supports pagination via offset and limit. |
| cancel_searchA | Cancel a running search job and free server-side resources. |
| check_connectionA | Verify that the Sumo Logic API connection is working. Tests authentication and endpoint reachability. Use this to confirm credentials are configured correctly. |
| get_account_usageA | Get account status and data ingestion information. |
| validate_queryA | Check if a Sumo Logic query is syntactically valid. Creates a minimal search job (1-second range) and immediately cancels it. Returns valid=true if the query was accepted, or the specific error message if it was rejected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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