Indicate

Server Details

AI-powered intelligence for your development workflow via Indicate.

Status: Healthy
Last Tested: 2026-03-27 17:30
Transport: Streamable HTTP
URL

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

5 tools

health_checkInspect

Check connectivity to the Indicate backend. Returns 'ok' if the server can reach the API, or an error message otherwise. Does not require authentication.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

list_data_sourcesInspect

Step 2 — List data sources available within a tenant. (In the Indicate system a data source is called a 'data product'.) Examples: Google Analytics, Facebook Ads, vioma, Booking.com. Returns each data source's 'id', 'displayName', and 'semantic_context_id'. → Pass the chosen 'id' as 'data_source_id' and 'semantic_context_id' to list_metrics.

ParametersJSON Schema

Name	Required	Description	Default
`tenant_id`	Yes	Tenant ID obtained from list_tenants.

list_metricsInspect

Step 3 — List metrics and their dimensions for a data source. (In the Indicate system a metric is called a 'data cube'.) Each metric includes its dimensions; every dimension has a 'scope' that is either 'perspective' or 'group'. → Pass the metric 'id' as 'metric_id' to query_metric. → Pass dimension IDs with scope='perspective' as 'perspective_dimension_id' and scope='group' as 'group_dimension_id' to query_metric.

ParametersJSON Schema

Name	Required	Description
`tenant_id`	Yes	Tenant ID from list_tenants.
`data_source_id`	Yes	Data source ID from list_data_sources.
`semantic_context_id`	Yes	Bounded context ID from the 'semantic_context_id' field in the list_data_sources response.

list_tenantsInspect

Step 1 — List all tenants the authenticated user can access. (In the Indicate system a tenant is called a 'space'.) Returns each tenant's 'id' and 'displayName'. → Pass the chosen tenant 'id' as 'tenant_id' to every subsequent tool call.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

query_metricInspect

Step 4 — Fetch time-series data for a specific metric. All IDs are obtained from the previous steps in the workflow. Optionally filter by date range (YYYY-MM-DD). Returns daily-granularity data points.

ParametersJSON Schema

Name	Required	Description
`end_date`	No	End date in YYYY-MM-DD format. Optional — omit for all available data.
`metric_id`	Yes	Metric ID from list_metrics (the 'id' field of a metric object).
`tenant_id`	Yes	Tenant ID from list_tenants.
`start_date`	No	Start date in YYYY-MM-DD format. Optional — omit for all available data.
`data_source_id`	Yes	Data source ID from list_data_sources.
`group_dimension_id`	Yes	Dimension ID where scope='group', from the dimensions array in the list_metrics response.
`semantic_context_id`	No	Bounded context ID (for reference / logging).
`perspective_dimension_id`	Yes	Dimension ID where scope='perspective', from the dimensions array in the list_metrics response.

Verify Ownership

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.

Server Details

Available Tools

Verify Ownership

Discussions

Your Connectors

Resources