Cohesity Gaia MCP (Preview)

Connect Copilot Studio agents to Cohesity Gaia Data Insights through a Model Context Protocol (MCP) server. Agents discover tools at runtime and query datasets, run LLM Q&A, and search indexed documents using your Gaia API key.

This connector is available in the following products and regions:

Architecture Overview

The Gaia MCP server acts as a bridge between MCP clients such as Copilot Studio and the Gaia REST API. MCP clients communicate with the server using the Model Context Protocol over Streamable HTTP at the /mcp endpoint. The server is implemented with FastMCP and runs with stateless_http=True.

Each MCP tool maps to a specific Gaia REST operation that is explicitly marked with x-mcp-tool: true in the Gaia OpenAPI specification. Tool names and descriptions can be customized using x-mcp-config.

When a client invokes a tool, the MCP server processes the JSON‑RPC request and calls the corresponding Gaia REST API using the configured api.base_url. The server forwards most incoming HTTP headers so that authentication and authorization remain consistent between MCP-based access and direct REST API usage.

Available MCP tools

The MCP server generates tools only for OpenAPI operations marked with x-mcp-tool: true.

| MCP tool | OpenAPI operationId | Method | Gaia Path | |---------------------|---------------------------|--------|-------------------------| | gaia_datasets | GetDatasets | GET | /datasets | | gaia_dataset_topics | GetDatasetDiscoveryResults| GET | /dataset/{id}/discovery | | gaia_ask | QueryLlm | POST | /ask | | gaia_search | ExhaustiveSearch | PUT | /ask/exhaustive | Note: All tools require the GAIA_VIEW privilege.

Authentication and Headers

Required by Gaia

Gaia uses an API key–based security scheme (ApiKeyAuth) as defined in the OpenAPI specification.

Clients must include the following header:

• apiKey: Your Gaia API key

gaia_datasets

• Purpose: Lists datasets and serves as the entry point for other Gaia tools.
• Visible Parameters: All query parameters from the OpenAPI specification except those hidden through x-mcp-config.hidden-params (statuses, sortField, sortOrder).
• Defaults: pageSize: 20 is applied through query-defaults if not supplied.
• Response: Trimmed to the GetDatasetsResponse model.

gaia_dataset_topics

• Purpose: Returns hierarchical topics for a dataset.
• Path parameter: id must be the dataset hex ID returned by gaia_datasets, not the display name.
• Defaults: level: 1, numLevels: 2.
• Hidden parameters: uuid.
• Dependencies (informational): GetDatasets, GetDatasetDetails.

gaia_ask

• Purpose: Executes an LLM query across one or more datasets
• Request body: LlmQueryParams with required fields:
  • datasetNames (array)
  • queryString
• Hidden fields: llmId, llmName, llm, conversationId, queryLanguageCode, history, metadata.
• Response: Filtered to the QueryLlmResponse schema (answer text, supporting documents, progress, and identifiers).

gaia_search

• Purpose: Performs an exhaustive search within a dataset.
• Request body: ExhaustiveSearchParams with required fields:
  • datasetName
  • queryString
  • pageSize (default 10 injected through query-defaults)
• Hidden fields: conversationId.
• Response: Filtered to the ExhaustiveSearchResponse schema (documents, pagination tokens, and IDs).

Creating a connection

The connector supports the following authentication types:

Default

Applicable: All regions

Parameters for creating connection.

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Throttling Limits

Actions

Cohesity Gaia MCP