cribl-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRIBL_BASE_URL | Yes | The base URL of your Cribl cloud instance | |
| CRIBL_AUTH_TYPE | Yes | The authentication type to use (e.g., cloud) | |
| CRIBL_CLIENT_ID | Yes | The client ID for authentication | |
| CRIBL_CLIENT_SECRET | Yes | The client secret for authentication |
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 |
|---|---|
| cribl_listWorkerGroupsA | Lists available worker groups in the Cribl deployment, optionally filtered by product type (stream, edge, search, or all). |
| cribl_getPipelinesB | Fetches pipeline definitions in a specified worker group. |
| cribl_getSourcesA | Fetches source configurations in a specified worker group. |
| cribl_getPipelineConfigB | Retrieves full configuration JSON for a specified pipeline in a worker group. |
| cribl_setPipelineConfigB | Applies a new configuration payload to a specified pipeline in a worker group. |
| cribl_restartWorkerGroupB | Restarts all workers within the default or specified worker group. |
| cribl_getSystemMetricsA | Retrieves system metrics from the Cribl deployment. IMPORTANT: To avoid excessively large responses, please use the optional parameters (filterExpr, metricNameFilter, earliest, latest, numBuckets, wp) to narrow down your query whenever possible. If no parameters are provided, the server will default to fetching only the most recent data bucket (numBuckets=1) to prevent performance issues. |
| cribl_versionControlA | Detects if version control (git) is enabled on the Cribl instance and whether a remote repository URL is configured. |
| cribl_commitPipelineA | Commits staged pipeline config changes to version control with a message. Returns detailed commit information including branch, commit ID, and summary of changed files. |
| cribl_deployPipelineB | Deploys a specific committed configuration version to a worker group. Returns the list of ConfigGroup objects Cribl provides. |
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 10 tools
Each tool targets a distinct action and resource: commit, deploy, get config, get list, sources, metrics, worker groups, restart, set config, version control. No overlapping purposes.
All tools follow a consistent 'cribl_verbNoun' pattern with camelCase (e.g., cribl_commitPipeline, cribl_getPipelines). Even 'cribl_versionControl' fits the pattern as a noun-based verb.
10 tools is well-scoped for a Cribl configuration and deployment server. It covers essential operations without being overwhelming or too sparse.
The tool set covers core pipeline lifecycle (get, set, commit, deploy), sources, worker groups, metrics, and version control. Missing are delete pipeline and potentially more granular worker group details, but the surface is solid for common use cases.