@grepr/cli 1.13.0-2632478 → 1.14.3-a181b29

package/build/dist/docs-index/4b490bf5-8866-4749-a717-23617a8974f3.txt

@@ -1,178 +0,0 @@
-Learn how to configure a Grepr OpenTelemetry integration to connect with Amazon CloudWatch, enabling you to ingest logs to a Grepr pipeline for processing and send the processed logs to a CloudWatch log group.
-
-# Configure Amazon CloudWatch connections with a Grepr integration
-
-To use Amazon CloudWatch as a destination for your Grepr pipelines, use the Grepr OpenTelemetry integration to ingest logs into your Grepr pipelines for processing and send the processed logs to CloudWatch. The OpenTelemetry integration supports receiving logs from any collector that supports OTLP/HTTP, such as the OpenTelemetry Collector and Fluent Bit, and sending the processed logs to a CloudWatch log group using the CloudWatch OTLP/HTTP endpoint.
-
-You can use the Grepr UI or REST API to create an OpenTelemetry integration configured for CloudWatch. To learn how to create an OpenTelemetry integration in the Grepr UI and configure collectors to send logs to Grepr, see [Use an OpenTelemetry integration with CloudWatch in a Grepr pipeline](#use-cloudwatch-integration).
-
-> Although this page describes using an integration to create a pipeline for sourcing and sending data with a single observability platform, your pipelines can use multiple integrations to source and sink data for different platforms. For example, you can create a pipeline with a Datadog integration that's used to source data from Datadog agents, and a Splunk integration and sink that sends the pipeline output to Splunk.
-
-## Requirements
-
-Connecting Grepr to CloudWatch uses CloudWatch's OTLP/HTTP endpoint, and requires the following:
-
-* The CloudWatch OTLP logs endpoint for your region.
-* An Amazon CloudWatch log group and log stream. The log group must have bearer token authentication enabled.
-* An AWS IAM user with `logs:PutLogEvents` permission on the CloudWatch log group and a bearer token to authenticate the user to CloudWatch.
-
-To learn more about the CloudWatch support for OTLP/HTTP, see [OTLP Endpoints](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-OTLPEndpoint.html).
-
-To learn more about creating an IAM user, bearer token, and the log group and stream for CloudWatch's OTLP/HTTP endpoint, see [Setting up bearer token authentication](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL_HTTP_Endpoints_BearerTokenAuth.html).
-
-## Use an OpenTelemetry integration with CloudWatch in a Grepr pipeline \[#use-cloudwatch-integration]
-
-### Step 1: Create an OpenTelemetry integration
-
-To create an OpenTelemetry integration configured for CloudWatch in the Grepr UI:
-
-1. Go to the **Integrations** page in the Grepr UI and click **Add new** next to **Observability Vendors**.
-
-2. In the **Add Observability Vendor** dialog:
-
-   * In the **Type** menu, select **Open Telemetry**.
-
-   * In the **Name** field, enter a name for the integration. Grepr recommends naming it descriptively so it's easy to identify. For example, `cloudwatch-prod-logs`.
-
-   * In the **Base Endpoint URL** field, enter `https://logs.<region>.amazonaws.com`, replacing `<region>` with your AWS region.
-
-   * Click **Add Header** and add the following three headers. For the `Authorization` header, select the lock icon to securely store the token.
-
-     * **Header Name**: `Authorization`. **Header Value**: `Bearer <bearer-token>`. Replace `<bearer-token>` with the bearer token for the CloudWatch IAM user.
-     * **Header Name**: `x-aws-log-group`. **Header Value**: the name of your CloudWatch log group.
-     * **Header Name**: `x-aws-log-stream`. **Header Value**: the name of your CloudWatch log stream.
-
-     To send logs from a single integration to dynamically chosen log groups or log streams based on log content, configure `x-aws-log-group` or `x-aws-log-stream` as attribute-sourced headers instead of static values.
-
-   * In the **Output encoding** menu, select **JSON**.
-
-3. Click **Create**.
-
-4. Save the `GREPR TOKEN` displayed in the confirmation dialog securely.
-
-   #### Optional: Grant team access to the integration
-
-   When you have teams in your Grepr organization, you can grant access to the integration to one or more of those teams. To configure team access when you create or edit an integration:
-
-   1. In the **Grant Team Access** section, click the plus sign icon (+).
-
-   2. Select the team or teams that should be granted access to the integration.
-
-   3. Click **Create**.
-
-   To learn more, see [Manage teams in the Grepr platform](/admin/manage-teams) and [Permissions in the Grepr platform](/grepr-platform/permissions).
-
-CloudWatch's OTLP endpoint determines the destination log group and log stream from the `x-aws-log-group` and `x-aws-log-stream` request headers. If you configure static values for these headers, your Grepr integration sends every log event to the same log group and log stream.
-
-To route log events from your integration to dynamically chosen CloudWatch log groups or log streams based on attributes included in the events, select **From Attribute** and enter the **Attribute Path** value when you configure the `x-aws-log-group` or `x-aws-log-stream` headers. Grepr groups log events that share the same attribute value into the same outbound request, sets the header to that value, and forwards the events to CloudWatch.
-
-For example, to send log events from a Kubernetes namespace to a log stream named after the namespace:
-
-1. In the Grepr OpenTelemetry integration, edit the `x-aws-log-stream` header.
-2. In the **Source** menu, select **From Attribute**.
-3. In the **Attribute Path** field, enter the path to the attribute that holds the namespace. For example, `kubernetes.namespace.name`.
-4. Save the header.
-
-When a log event is missing the configured attribute, Grepr still delivers the event to the CloudWatch endpoint, but without the `x-aws-log-stream` header. Because the CloudWatch OTLP endpoint relies on this header to determine the destination log stream, ensure every log event routed through the integration contains the required attribute, or use a static value for `x-aws-log-stream`.
-
-### Step 2: Add a source to your pipeline
-
-To add a source to your pipeline that uses the OpenTelemetry integration:
-
-1. In the Grepr UI, go to the details page of an existing pipeline or create a new pipeline from the homepage.
-2. In the left-hand navigation menu, click **Sources**.
-3. In the **Add source** dialog, select your OpenTelemetry integration in the **Source** menu.
-4. Click **Submit**.
-
-### Step 3: Configure log forwarding to Grepr
-
-To send data to Grepr, you configure your collector or agent to send it to the ingestion URL for your Grepr integration, rather than to your observability vendor's platform. To find the ingestion URL when using the Grepr UI to configure your pipeline, go to the details page for the pipeline, click **Sources** in the left pane, and copy the **Ingest URL**.
-
-
-
-If you connect to Grepr through AWS PrivateLink, copy the private ingestion URL and use it in place of the public ingestion URL. To learn more about sending data to Grepr over AWS PrivateLink, see [Securely forward observability data to Grepr with AWS PrivateLink](/admin/private-link).
-
-When you use the API, you can construct the ingestion URL using the following format:
-
-`https://<integration-id>-<org-id>.ingest.grepr.ai/otlp`
-
-Replace `<integration-id>` with the identifier of the vendor integration used by your pipeline and replace `<org-id>` with the identifier for your organization.
-
-To use the PrivateLink endpoint service, insert `.private` after the `ingest` host segment.
-
-Although all sources created from the same integration share the same ingestion URL, you can use a single integration to create sources for multiple pipelines. The Grepr platform ensures events are routed to the correct pipelines.
-
-Authenticate by sending the Grepr token in the `x-grepr-token` header. Replace `<grepr-token>` in the examples below with the token you saved after creating the OpenTelemetry integration in Step 1.
-
-To see more information and configuration examples, select the tab for your preferred log collector:
-
-The OpenTelemetry Collector can send logs to Grepr using the `otlphttp` exporter.
-
-To configure the OpenTelemetry Collector to send logs to Grepr's ingestion endpoint, update your collector configuration (`collector.yaml`):
-
-```yaml
-exporters:
-  otlphttp:
-    endpoint: <ingestion-url>
-    headers:
-      x-grepr-token: <grepr-token>
-
-service:
-  pipelines:
-    logs:
-      receivers: [otlp]
-      processors: [batch]
-      exporters: [otlphttp]
-```
-
-Replace `<ingestion-url>` with the full ingestion URL provided by the Grepr UI, and `<grepr-token>` with your Grepr token.
-
-To learn more about OpenTelemetry Collector configuration, see the [OpenTelemetry Collector documentation](https://opentelemetry.io/docs/collector/).
-
-Fluent Bit can forward logs to Grepr using the OpenTelemetry output plugin. To configure the plugin:
-
-* Set the `host` value using only the hostname of the ingestion URL from your OpenTelemetry integration, omitting the `https://` prefix and the path value.
-* Set the `logs_uri` value to the ingestion URL path and append `/v1/logs`.
-* Add a `header` entry that sends the Grepr token as `x-grepr-token`.
-
-The following is an example `OUTPUT` configuration for the OpenTelemetry plugin from a Fluent Bit configuration file (`fluent-bit.conf`):
-
-```ini
-[OUTPUT]
-  name                 opentelemetry
-  match                *
-  host                 <integration-id>-<organization-id>.ingest.grepr.ai
-  port                 443
-  logs_uri             /otlp/v1/logs
-  header               x-grepr-token <grepr-token>
-  tls                  On
-  tls.verify           On
-```
-
-To learn more about configuration settings for Fluent Bit, see the documentation for the [Fluent Bit OpenTelemetry output plugin](https://docs.fluentbit.io/manual/data-pipeline/outputs/opentelemetry).
-
-## Frequently Asked Questions
-
-### How do I connect Grepr to Amazon CloudWatch?
-
-Create an OpenTelemetry integration in Grepr with the CloudWatch OTLP endpoint, https\://logs.\<region>.amazonaws.com, and configure three headers: an Authorization header with a bearer token stored securely with the lock icon, an x-aws-log-group header with the log group name, and an x-aws-log-stream header with the log stream name. Set Output encoding to JSON. You must enable bearer token authentication on the log group in AWS before sending logs.
-
-### Why does Grepr require bearer token authentication for CloudWatch?
-
-CloudWatch's OTLP endpoint requires bearer token authentication rather than standard IAM access keys. The bearer token authenticates an IAM user that has logs:PutLogEvents permission on the target log group.
-
-### What output encoding should I use for the CloudWatch integration?
-
-Use JSON. When you create the OpenTelemetry integration for CloudWatch, select JSON in the Output encoding menu so Grepr sends log events to the CloudWatch OTLP endpoint in JSON format.
-
-### Does Grepr create CloudWatch log groups automatically?
-
-No. You must create the CloudWatch log group and log stream in AWS before Grepr can send logs to them. You must also enable bearer token authentication on the log group.
-
-### Can I use an existing CloudWatch log group with Grepr?
-
-Yes. Enable bearer token authentication on the existing log group, and create the log stream if it does not already exist.
-
-### How do I route logs to different CloudWatch log groups or log streams?
-
-Configure the x-aws-log-group or x-aws-log-stream header as an attribute-sourced header. In the header configuration, select From Attribute and enter the Attribute Path for the attribute that holds the destination value, such as kubernetes.namespace.name. Grepr groups events that share the same attribute value into the same request and sets the header to that value. If an event is missing the attribute, Grepr delivers it without that header, so use a static value when an event might not include the attribute.

package/build/dist/docs-index/4b63606f-4d87-4274-ba3f-2a019e8bce8a.json

@@ -1 +0,0 @@
-{"docType":"doc"}

package/build/dist/docs-index/4b63606f-4d87-4274-ba3f-2a019e8bce8a.txt

@@ -1,113 +0,0 @@
-Process data in Grepr pipelines using built-in tools for parsing, filtering, enrichment, and transformation of log events.
-
-# Transform data in a Grepr pipeline
-
-A Grepr transform is a processing step that modifies, enriches, or restructures data as it flows through a pipeline. As records move through a pipeline, transforms allow you to parse structured and semi-structured data, filter records, and use a familiar SQL interface to perform more complex transformation of records as they move through a pipeline. Transforms are configured as pipeline steps that process data sequentially. Each transform receives input data, applies its logic, and passes the result to the next step in the pipeline.
-
-Most transforms are available in the Grepr pipelines UI. Some transforms are available only in the Grepr REST API or provide more capabilities when used with the API, such as [filters](#filter) and [branching the processing of records](#message-routing) based on query matches.
-
-The following sections describe the transforms available in Grepr pipelines.
-
-## Transform semi-structured records with the Grok parser \[#grok-parser]
-
-The Grok transform parses unstructured text using pattern matching with regular expressions and named capture groups. Use this transform to extract fields from log lines, error messages, and other text-based data where you need to identify specific patterns and convert them to structured fields.
-
-See [Grok parser](/transforms/grok).
-
-## Convert JSON messages into structured objects \[#json-parser]
-
-The JSON parser transforms JSON strings into structured JSON objects. This transform handles nested objects, arrays, and various data types, making it useful for processing API responses, configuration data, and structured log entries.
-
-See [Transform JSON strings into JSON objects](/transforms/json-parsing).
-
-## Restructure JSON objects with a remapper \[#remapper]
-
-The remapper transform moves or copies attributes to top-level fields or to tags in a JSON object. You can also use rename rules to move attribute values from one path to another within the same event. In the pipelines UI, a remapper with customizable default attributes is automatically added to a pipeline.
-
-See [Remap JSON attribute fields to top-level log event fields](/transforms/remapper).
-
-## Transform records with SQL \[#sql-transform]
-
-The SQL transform allows you to use ANSI standard SQL queries to filter, transform, and enrich data records. The SQL transform provides a familiar SQL interface to perform a number of data processing and transformation tasks.
-
-You can use the SQL transform in the Grepr UI or REST API. In the UI, the SQL transform is available when you configure filters.
-
-To learn about using the SQL transform in the Grepr API, see the [SQL Operation specification](/apis/api-spec#schema/SQLOperation).
-
-For a complete reference and examples, see [Transform events with SQL](/transforms/sql-transform).
-
-## Filter records based on conditions \[#filter]
-
-The Filter transform includes or excludes data records based on specified conditions. You can create filters using familiar query interfaces, such as SQL, as well as Datadog and New Relic log query-like syntaxes.
-
-In the Grepr pipelines UI, you filter records with actions, which are available at three locations in a pipeline. To learn how to configure actions, see [Filter and transform events with actions](/transforms/filter-events).
-
-To have more flexibility for where filters are included in a pipeline, use the REST API. See [LogsFilter](/apis/api-spec#schema/LogsFilter).
-
-## Reduce log volumes with dynamic aggregation \[#reducer]
-
-The Grepr log reducer uses clustering algorithms to identify patterns in your log data and aggregate similar log messages. The output of this aggregation includes summaries and samples of similar messages. The log reducer is a core step in a log reduction pipeline, where it runs before processed log events are sent to your configured sinks. By sending summaries of similar messages rather than multiple events with redundant information, Grepr significantly reduces the volume of shipped logs and your observability costs. The log reduction pipeline also persists the complete set of raw logs to a low-cost data lake, enabling you to analyze and troubleshoot issues when necessary.
-
-To learn more about how Grepr reduces log volumes with dynamic aggregation, see [Reduce noise and improve the usability of your logs with the log reducer](/transforms/reducer).
-
-To learn how to create a log reduction pipeline, see [Tutorial: Build your first Grepr pipeline](/tutorials/first-pipeline).
-
-To learn how to use the resulting summarized log events in your observability platform along with raw logs stored in Grepr, see [Troubleshoot incidents with Grepr-processed data and your observability tool](/tutorials/troubleshooting-example).
-
-## Transform and enrich log messages with the REST API \[#log-transform-action]
-
-You can use the LogTransformAction in the REST API to specify actions that transform log messages, such as adding or removing attributes and tags. See [LogTransformAction](/apis/api-spec#schema/LogTransformAction).
-
-## Route the processing of messages based on query matches \[#message-routing]
-
-You can route log messages to be processed by different pipelines based on query matches. Because the pipelines UI doesn't support branching, Grepr recommends creating multiple pipelines that ingest data using the same source, and then use filters to route data to the correct pipeline.
-
-Sending logs to different destinations, rather than processing them differently, is a separate problem with its own approaches. See [_](/solution-guides/route-logs-to-several-accounts).
-
-You can also use the REST API to create more complex pipeline configurations. See [LogsBranch](/apis/api-spec#schema/LogsBranch).
-
-## Frequently Asked Questions
-
-### What transforms are available in Grepr pipelines?
-
-Grepr provides several transform types: Grok parser for parsing unstructured text with pattern matching, JSON parser for converting JSON strings into structured objects, remapper for restructuring JSON fields and attributes, SQL transform for complex filtering and enrichment using SQL queries, and Filter transform for conditional record processing. Most transforms are available in the UI, while some advanced options are available via REST API.
-
-### When should I use the Grok parser transform?
-
-Use the Grok parser when you need to extract structured data from unstructured text logs. It's ideal for parsing error messages, application logs, system logs, and other text-based data where you need to identify specific patterns and convert them into structured fields using regular expressions and named capture groups.
-
-### When should I use the JSON parser transform?
-
-Use the JSON parser when your log messages contain JSON strings that need to be converted into structured JSON objects. This is useful for processing API responses, configuration data, and structured log entries. The JSON parser handles nested objects, arrays, and various data types automatically.
-
-### What is the remapper transform and when is it used?
-
-The remapper transform moves or copies attributes to top-level fields or to tags in a JSON object. It's useful for standardizing log event structure by moving well-known fields like message, severity, and host from nested attributes to top-level fields. You can configure whether the source attribute is preserved or removed after remapping. The remapper also supports rename rules for moving attribute values from one path to another. The remapper is automatically added to pipelines in the UI with customizable default attributes.
-
-### When should I use the SQL transform?
-
-Use the SQL transform when you need complex filtering, transformation, or enrichment of log records. SQL provides a familiar interface for advanced operations like conditional logic, string manipulation, aggregations, and joining data. It's available in the UI for filters and via REST API for more flexibility.
-
-### Can I combine multiple transforms in a pipeline?
-
-Yes, transforms are configured as sequential pipeline steps. Each transform receives input from the previous step, applies its logic, and passes the result to the next step. This allows you to create complex data processing workflows by combining parsing (Grok), restructuring (remapper), and filtering/enrichment (SQL) transforms.
-
-### What is the Filter transform used for?
-
-The Filter transform includes or excludes data records based on specified conditions. You can use filters with SQL, Datadog, and New Relic-like query syntaxes. In the UI, filters are located in predefined pipeline positions, while the REST API provides more flexibility for filter placement.
-
-### Can I use the REST API for more advanced transform options?
-
-Yes, the REST API provides access to advanced transform options not available in the UI. For example, you can use LogTransformAction to add or remove attributes and tags, LogsBranch for complex message routing based on query matches, and more flexible filter placement. See the API specification for complete details on transform capabilities.
-
-### How do I choose between Grok and SQL transforms?
-
-Use Grok when you need pattern-based parsing of unstructured text to extract specific fields. Use SQL when you need complex conditional logic, calculations, string transformations, or filtering. Grok is specialized for text parsing, while SQL is more general-purpose for data manipulation and enrichment.
-
-### How does Grepr reduce log volumes and observability costs?
-
-Grepr uses clustering algorithms to identify patterns in log data and aggregates similar log messages. Instead of sending multiple redundant log events, Grepr sends summaries and samples of similar messages to your observability platform. This significantly reduces the volume of shipped logs while retaining the ability to analyze and troubleshoot issues. Raw logs are retained in a low-cost data lake for future reference.
-
-### What happens if a transform fails on a record?
-
-Transform behavior depends on the specific transform type and configuration. Parsing errors (like Grok or JSON parsing) typically skip records or add error attributes depending on your configuration. SQL transforms filter out records that don't match conditions. Review transform-specific documentation for error handling details.

package/build/dist/docs-index/4b88ce61-4969-4387-b621-c502f32eed60.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/4b88ce61-4969-4387-b621-c502f32eed60.txt

@@ -1,15 +0,0 @@
-# DatasetCreate
-
-**Type**: `object`
-
-## Properties
-
-- name: integrationId (required)
-  type: string
-
-- name: name (required)
-  type: string
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this dataset is associated with.

package/build/dist/docs-index/4b8d51bc-e80e-486e-9386-09146a273f04.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/4b8d51bc-e80e-486e-9386-09146a273f04.txt

@@ -1,22 +0,0 @@
-# IntegrationExceptionsList
-
-Paginated list of vendor imported exceptions for an integration
-
-**Type**: `object`
-
-## Properties
-
-- name: exceptions (optional)
-  type: `ItemsCollectionVendorImportedException`
-
-- name: hasMore (optional)
-  type: boolean
-  description: Whether there are more pages available
-
-- name: page (optional)
-  type: integer
-  description: Current page number (0-based)
-
-- name: pageSize (optional)
-  type: integer
-  description: Number of items per page

package/build/dist/docs-index/4bb17f73-fec5-47e4-9264-66a086fb9802.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/4bb17f73-fec5-47e4-9264-66a086fb9802.txt

@@ -1,39 +0,0 @@
-# Set a Datadog integration's API keys
-
-**PUT** `/v1/integrations/datadog/{id}/api-keys`
-
-**Operation ID**: `setDatadogApiKeys`
-**Summary**: Set a Datadog integration's API keys
-Replaces the integration's entire set of API keys in one atomic write. Existing keys are referenced by id (kept or rotated), new keys carry only a value, and omitted keys are removed; one key is marked as the send key used to write data back to Datadog. If any key is rejected the existing set is left unchanged. All keys are accepted for inbound telemetry. Requires the organization to have multiple Datadog API keys enabled. Adding, removing, relabeling, or rotating a key other than the send key is allowed while the integration's pipeline is running; a change that affects the send key (which key it is, or its value) requires the pipeline to be stopped, since that key is baked into the running Flink job.
-
-## Tags
-- Datadog Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `SetApiKeysRequest`
-
-## Responses
-
-### 200
-
-API keys updated successfully
-
-- **Content-Type**: `application/json` / `ReadDatadog`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration or a referenced key not found.
-
-### 409
-
-The key count exceeds the limit, or the change affects the send key while the integration is in use by a running pipeline.

package/build/dist/docs-index/4bd77b96-8d17-45ff-ae23-4554a8003f89.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/4bd77b96-8d17-45ff-ae23-4554a8003f89.txt

@@ -1,24 +0,0 @@
-# WriteDatadog
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-  description: Name of the integration.
-
-- name: payload (required)
-  type: `Datadog`
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this integration is associated with.
-
-- name: type (required)
-  type: enum: `datadog`
-  description: The type of the integration. This is used to determine the payload type.
-
-- name: version (required)
-  type: integer
-  description: Version of the integration. Should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.

package/build/dist/docs-index/4c296dab-ef12-47bb-8482-66d533b7d80a.json

@@ -1 +0,0 @@
-{"docType":"doc"}

package/build/dist/docs-index/4c296dab-ef12-47bb-8482-66d533b7d80a.txt

@@ -1,229 +0,0 @@
-Connect Claude, Claude Code, Cursor, Codex, or ChatGPT to the Grepr MCP server with OAuth sign-in, or connect any MCP client with a service account token.
-
-# Connect to the Grepr MCP server
-
-Grepr provides a remote Model Context Protocol server, or MCP server, that lets AI assistants work with your Grepr organization. The server provides tools to list pipelines, browse datasets and templates, query logs, validate SQL and Grok rules, and propose pipeline changes. Every tool call is authorized with the same role-based permissions as the Grepr UI and REST APIs.
-
-The MCP server is available at the following endpoints:
-
-| Region | Endpoint |
-| --- | --- |
-| US | `https://app.grepr.ai/mcp` |
-| EU | `https://app.euc1.grepr.ai/mcp` |
-
-The examples on this page use the US endpoint. If your organization is in the EU region, replace the endpoint and use the EU client ID.
-
-You can authenticate in two ways:
-
-* OAuth sign-in: You sign in interactively with your Grepr user account. Use this for Claude, Claude Code, Cursor, Codex, and ChatGPT.
-* Service account credentials: Your client authenticates as a Grepr service account. Use this for Claude Tag in Slack, for automation, and for MCP clients that do not support the OAuth sign-in flow.
-
-## Sign in with OAuth
-
-Grepr registers a dedicated OAuth client for each supported MCP client. To connect, configure your MCP client with the Grepr endpoint and the matching client ID from the following table, then sign in with your Grepr user account. When the sign-in page prompts for an organization, enter your Grepr organization name.
-
-| MCP client | US client ID | EU client ID |
-| --- | --- | --- |
-| Claude | `us3sBOgZj6hERktG9yZEVwujaJe3j9L0` | `HOnxCPNGnzdGlfXBM2sff0twoolRnDj9` |
-| Claude Code | `jlCTdLYzDkkTSc2I7MdI0SBw48AOdJM6` | `GlEIcfSbge5gqN4o918fLXKVONP2twBh` |
-| Cursor | `ol2iI3MgbY4gDMT1SbCDQHj5OA8K4bAg` | `XHHImmxqr9EihBqVOettpLhS6CxDBhoB` |
-| Codex | `QPTtqmepPCvjvAs4rJHfBwXC4HklKefA` | `V0JSLGp1GmySuCj8tJPGqTXXMuP6unRx` |
-| ChatGPT | `R3rgytuEh03CzvNrasYj8R3eeAaYVcAP` | `7GCueSSV94VNsv2TkLGnWiWlyoS3DQrA` |
-
-### Claude
-
-These steps apply to Claude on the web, the Claude desktop apps, and the Claude mobile apps.
-
-1. In Claude, go to **Settings** > **Connectors** and click **Add custom connector**.
-2. Enter `https://app.grepr.ai/mcp` as the URL.
-3. Under **Advanced settings**, enter `us3sBOgZj6hERktG9yZEVwujaJe3j9L0` as the **OAuth Client ID**. Leave the client secret empty.
-4. Complete the sign-in flow with your Grepr user account.
-
-### Claude Code
-
-Add the server with the Grepr client ID and the fixed callback port:
-
-```bash
-claude mcp add --transport http --client-id jlCTdLYzDkkTSc2I7MdI0SBw48AOdJM6 --callback-port 6280 grepr https://app.grepr.ai/mcp
-```
-
-The `--callback-port 6280` flag is required. Without it, Claude Code picks a random port and the sign-in fails with a callback URL mismatch.
-
-Then open Claude Code, run `/mcp`, select `grepr`, and complete the sign-in flow in your browser with your Grepr user account.
-
-### Cursor
-
-Add the server with the Grepr client ID to `~/.cursor/mcp.json`, or to `.cursor/mcp.json` in a project:
-
-```json
-{
-  "mcpServers": {
-    "grepr": {
-      "url": "https://app.grepr.ai/mcp",
-      "auth": {
-        "CLIENT_ID": "ol2iI3MgbY4gDMT1SbCDQHj5OA8K4bAg"
-      }
-    }
-  }
-}
-```
-
-The `auth` block with `CLIENT_ID` is required. Without it, Cursor tries dynamic client registration, which Grepr does not support, and the sign-in fails. Do not add a client secret. Cursor uses fixed callback URLs that Grepr registers, so you do not need to set a callback port.
-
-Save the file and restart Cursor. The `grepr` server shows in **Customize** > **MCPs**. When Cursor prompts you to sign in, complete the sign-in flow in your browser with your Grepr user account.
-
-### Codex
-
-Add the server with the Grepr client ID and the fixed callback port to `~/.codex/config.toml`:
-
-```toml
-[mcp_servers.grepr]
-url = "https://app.grepr.ai/mcp"
-
-[mcp_servers.grepr.oauth]
-client_id = "QPTtqmepPCvjvAs4rJHfBwXC4HklKefA"
-callback_port = 6280
-```
-
-The `callback_port = 6280` setting is required. Without it, Codex picks a random port and the sign-in fails with a callback URL mismatch. Use the endpoint for your region exactly as the endpoint table writes it, with no trailing slash, because Codex builds its callback URL from the endpoint URL.
-
-Then sign in:
-
-```bash
-codex mcp login grepr
-```
-
-Complete the sign-in flow in your browser with your Grepr user account.
-
-### ChatGPT
-
-Your ChatGPT plan or workspace settings must allow custom MCP servers.
-
-1. In ChatGPT, go to **Plugins**, click **Add**, and select **Add custom MCP server**.
-2. Enter a name such as `Grepr`, and enter `https://app.grepr.ai/mcp` as the **Server URL**. Enter the endpoint for your region exactly as the endpoint table writes it, because ChatGPT builds its callback URL from it. Keep **OAuth** as the **Authentication**.
-3. Open **Advanced OAuth settings** and keep **User-Defined OAuth Client** as the **Registration method**. Enter `R3rgytuEh03CzvNrasYj8R3eeAaYVcAP` as the **OAuth client ID**, leave the client secret empty, and keep `none` as the **Token endpoint auth method**.
-4. Select **I understand and want to continue** and click **Create as a plugin**.
-5. When ChatGPT prompts you to sign in, complete the sign-in flow with your Grepr user account.
-
-## Connect Claude Tag in Slack
-
-Claude Tag is Claude in Slack channels. In a channel, Claude acts as a shared identity that an Owner of your Claude organization configures, not as the person who sends the message. Everyone in a channel that the configuration covers gets the same Grepr access, so connect a dedicated Grepr service account with the narrowest role that fits the channel. Direct messages with Claude in Slack run on your own Claude account and use the Claude connector described earlier on this page.
-
-Before you start, you need:
-
-* The Owner role in your Claude organization. Claude Tag is available on the Claude Team and Enterprise plans.
-* A Grepr service account and its client ID and client secret. See [Manage Grepr service accounts](/admin/service-accounts).
-* The Grepr plugin for Claude Tag: [grepr-claude-tag-plugin.zip](/plugins/grepr-claude-tag-plugin.zip). Claude Tag reaches an MCP server only through a plugin. The plugin contains two files: a manifest, and an `.mcp.json` file that names the US and EU Grepr MCP endpoints.
-
-### Upload the plugin
-
-1. In Claude, go to **Admin settings** > **Plugins** and click **Add plugins**.
-2. Select **Upload a file** and upload `grepr-claude-tag-plugin.zip`.
-
-The plugin is now in your organization's catalog. It does nothing until you turn it on in an access bundle.
-
-### Turn on the plugin and add the credential
-
-An access bundle is the set of credentials and plugins that Claude uses in the channels the bundle covers. The **Default Slack** scope covers every channel in your Slack workspace. To limit Grepr access to one channel, select that channel's scope instead.
-
-1. Go to **Admin settings** > **Claude Tag** and, under **Claude Tag's access**, select the **Slack** tab.
-
-2. Select the **Default Slack** scope, or the channel to connect.
-
-3. Next to **Access bundles**, click the **+** button and select **Create new bundle**, or open the existing bundle.
-
-4. On the **Plugins** tab, turn on **grepr-mcp**.
-
-5. On the **Credentials** tab, click **Connect** next to **Custom tool** and enter the following values:
-
-   \| Field | Value | | --- | --- | | Name | `Grepr` | | Credential type | **OAuth 2.0 client credentials** | | Token URL | `https://auth.grepr.ai/oauth/token`, or `https://auth.eu.grepr.ai/oauth/token` for the EU region | | Client ID | The service account client ID | | Client secret | The service account client secret | | Audience | `service` | | Allowed websites | `app.grepr.ai`, or `app.euc1.grepr.ai` for the EU region |
-
-6. Save the connection and confirm that its status is **Active** on the **Access bundles** page.
-
-> A bundle on a public channel gives its access to anyone who joins the channel. Keep a service account with edit permissions in a bundle on a private channel.
-
-### Test the connection
-
-In a channel the bundle covers, start a new thread and send:
-
-```text
-@Claude list the Grepr pipelines
-```
-
-Threads that started before you turned on the plugin do not pick it up. If Claude reports that a host was blocked by the network egress proxy, add the host it names to the **Allowed websites** of the Grepr connection.
-
-## Authenticate with a service account token
-
-For automation, and for MCP clients that are not in the table and do not support OAuth 2.0 client credentials, authenticate with a service account access token. The MCP endpoint accepts the same access tokens as the Grepr REST APIs.
-
-1. Create a service account. See [Manage Grepr service accounts](/admin/service-accounts).
-
-2. Obtain an access token. See [Authenticate to Grepr REST APIs](/apis/authentication).
-
-3. Configure your MCP client to send the token in the `Authorization` header. Most clients accept a headers object in their MCP server configuration:
-
-   ```json
-   {
-     "headers": {
-       "Authorization": "Bearer <access-token>"
-     }
-   }
-   ```
-
-> The access token expires after 24 hours and has no refresh token, so your client cannot renew it automatically. When the token expires, obtain a new token and update your client configuration. For scheduled automation, obtain a new token at the start of each run.
-
-## Use Grepr skills through the MCP server \[#skills]
-
-The MCP server also provides *skills*: instructions that teach an AI assistant how to work with Grepr efficiently. The server lists each skill in the instructions it sends when your client connects, and serves each skill's files as MCP resources at `skill://<skill-name>/SKILL.md`. MCP clients that read resources, such as Claude Code, load a skill when your request matches it.
-
-The server provides the following skills:
-
-* `cli`: Installs, configures, and signs in to the Grepr CLI, and points to the other Grepr skills.
-* `query`: Queries logs and spans with the Grepr CLI, scoped so that each query reads as little data as possible.
-* `query-predicate`: Translates a request into a Grepr query predicate.
-* `recover-reduced-logs`: Explains the summary logs that Grepr sends to your observability vendor in place of repeated logs, and finds the original logs behind a summary in the Grepr data lake.
-* `backfill-logs`: Sends original logs from the Grepr data lake to your observability vendor.
-
-When your AI assistant can run shell commands, the skills use the Grepr CLI instead of the MCP tools, because the CLI writes results to a file and has no page limit. To install the CLI, see [Grepr CLI](/cli). The [coding assistant plugins](/cli#agent-skills) include these skills and the rest of the Grepr skills.
-
-## Frequently Asked Questions
-
-### Does the Grepr MCP server provide skills?
-
-Yes. The server lists its skills in the instructions it sends when a client connects and serves each skill as an MCP resource at skill://\<skill-name>/SKILL.md. The skills cover setting up the Grepr CLI, querying logs and spans, building query predicates, recovering the original logs behind a Grepr summary, and backfilling logs to your observability vendor.
-
-### What is the Grepr MCP server URL?
-
-The MCP endpoint is https\://app.grepr.ai/mcp for the US region and https\://app.euc1.grepr.ai/mcp for the EU region.
-
-### How do I connect Claude to Grepr?
-
-Add a custom connector in Claude with the URL https\://app.grepr.ai/mcp, and enter the Grepr client ID for Claude under Advanced settings. Then sign in with your Grepr user account.
-
-### How do I connect Cursor to Grepr?
-
-Add the server to your Cursor mcp.json file with the URL https\://app.grepr.ai/mcp and an auth block that contains the Grepr client ID for Cursor. Then restart Cursor and, when it prompts you, sign in with your Grepr user account.
-
-### How do I connect Codex to Grepr?
-
-Add the server to your Codex config.toml file with the URL https\://app.grepr.ai/mcp, the Grepr client ID for Codex, and callback_port = 6280. Then run codex mcp login grepr and sign in with your Grepr user account.
-
-### How do I connect ChatGPT to Grepr?
-
-Add a custom MCP server in ChatGPT with the URL https\://app.grepr.ai/mcp and OAuth authentication. Under Advanced OAuth settings, keep User-Defined OAuth Client as the registration method and enter the Grepr client ID for ChatGPT. Then sign in with your Grepr user account.
-
-### Why does the MCP sign-in fail with a callback URL mismatch?
-
-Grepr registers exact OAuth callback URLs. Claude Code and Codex must use port 6280. In Claude Code, set it with the --callback-port 6280 flag. In Codex, set callback_port = 6280 in config.toml. Cursor and ChatGPT use callback URLs that Grepr registers, so they need no callback setting. Codex and ChatGPT build the callback URL from the server URL, so enter the endpoint for your region exactly as the endpoint table writes it.
-
-### Can I use the Grepr MCP server without OAuth?
-
-Yes. The MCP endpoint accepts the same service account access tokens as the Grepr REST APIs. Send the token in the Authorization header as a Bearer token.
-
-### Can I use Grepr from Claude in Slack?
-
-Yes. Upload the Grepr plugin for Claude Tag, turn it on in an access bundle, and add an OAuth 2.0 client credentials connection for app.grepr.ai with a Grepr service account, the token URL https\://auth.grepr.ai/oauth/token, and the audience service.
-
-### Which organization does an MCP session use?
-
-The organization you enter at sign-in, or the organization of the service account that issued the token. The MCP session is scoped to that organization.