SNC Cribl MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR) | INFO |
| CRIBL_PASSWORD | No | Password for authentication | |
| CRIBL_USERNAME | No | Username for authentication | |
| CRIBL_SERVER_URL | No | Base URL of your Cribl deployment | |
| CRIBL_TIMEOUT_MS | No | API request timeout in milliseconds | 10000 |
| CRIBL_VERIFY_SSL | No | Verify SSL certificates | true |
| CRIBL_BEARER_TOKEN | No | Pre-existing bearer token |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_groupsA | Return JSON describing all Stream worker groups and Edge fleets in the configured Cribl deployment. |
| list_sourcesA | Return JSON describing all configured Stream and Edge sources in all groups in the Cribl deployment. Includes both regular input sources and collector sources (S3, REST, database, etc.). |
| list_destinationsA | Return JSON describing all configured Stream and Edge destinations in all groups in the Cribl deployment. |
| list_pipelinesA | Return JSON describing configured Stream and Edge pipelines in all groups in the Cribl deployment. Optionally filter by pipeline_id to fetch a specific pipeline. |
| list_routesA | Return JSON describing all configured Stream and Edge routes in all groups in the Cribl deployment. |
| list_breakersB | Return JSON describing all configured Stream and Edge event breakers in all groups in the Cribl deployment. |
| list_lookupsA | Return JSON describing all configured Stream and Edge lookups in all groups in the Cribl deployment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| Summarize Cribl Configuration | Create a prompt to summarize the current Cribl configuration. |
| Find Broken Sources | Create a prompt to find broken sources. |
| Analyze Pipeline | Analyze a specific pipeline for best practices and potential issues. |
| Troubleshoot Destination | Help troubleshoot issues with a specific destination. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Cribl Groups | Return a JSON list of all worker groups and Edge fleets. |
| Cribl Sources | Return a JSON list of all configured sources. |
| Cribl Destinations | Return a JSON list of all configured destinations. |
| Cribl Pipelines | Return a JSON list of all configured pipelines. |
| Cribl Routes | Return a JSON list of all configured routes. |
| Cribl Event Breakers | Return a JSON list of all configured event breakers. |
| Cribl Lookups | Return a JSON list of all configured lookups. |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose targeting different Cribl resources: breakers, destinations, groups, lookups, pipelines, routes, and sources. The naming and descriptions make it unambiguous which resource each tool retrieves, with no overlap in functionality.
All tools follow a consistent 'list_<resource>' naming pattern in snake_case, making them predictable and easy to understand. This uniformity aids in agent selection and reduces confusion.
With 7 tools, the count is reasonable for a Cribl management server, covering key resources like sources, pipelines, and routes. However, it lacks CRUD operations beyond listing, which slightly limits its scope but keeps it focused.
The toolset is severely incomplete as it only provides read-only list operations for resources. There are no create, update, or delete tools, which are essential for managing a Cribl deployment, leading to significant gaps in agent workflows.