Skip to main content
Glama
Adjust MCP server

Adjust MCP server

by get-mcp-ads

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ADJUST_API_TOKENYesRequired. The API token of your Adjust user. It is a bearer credential with that user's reporting access.
ADJUST_APP_TOKENSYesRequired. Comma-separated app tokens this server may read, up to 200. Every request is checked against this list, and app discovery returns only these apps.
ADJUST_ENVIRONMENTNo`production` (default) or `sandbox`. Fixed for every report; a tool call cannot change it.production

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

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
adjust_list_appsA

List the Adjust applications in ADJUST_APP_TOKENS that this API token can read, with native currency and configured operating systems. Applications outside the allowlist are never returned.

adjust_list_eventsA

Discover native event base slugs, ordinary activity-count metric IDs and app-specific event tokens for one allowlisted Adjust app. Use activityMetric for counts; the event base slug alone is not a report metric. Keep SKAdNetwork and aggregate revenue definitions separate.

adjust_get_catalogA

Read documented standard Adjust dimensions and example metrics, plus event metrics scoped to one allowlisted application. Metrics and spend/revenue access remain subject to Adjust permissions; the standard metric list is not exhaustive.

adjust_run_reportB

Read an attribution/performance report for one allowlisted Adjust app. Preserves native totals, warnings, attribution options, currency and UTC offset. Missing metrics are null; ratios are native fractions. A truncated or partial result is not a complete extraction.

adjust_compare_periodsA

Compare two equal-length periods for one allowlisted Adjust application with identical metrics, filters, OS and measurement settings. Defaults to the immediately preceding period. Changes use native totals, never sums of breakdowns. Unavailable or partial values have no calculated change; cohort maturity and reporting delays still apply.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
adjust-guideHow to read Adjust reports with this server: tool order, scope, measurement settings and rate limits.

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation4/5

adjust_list_events and adjust_get_catalog both expose metric/event metadata, so there is slight overlap, but each has a clear scope: per-app events versus standard dimensions/metrics. adjust_run_report and adjust_compare_periods are clearly separated by single-period reporting versus two-period comparison.

Naming Consistency5/5

All five tools use the same adjust_ prefix and a consistent verb_noun pattern: list_apps, list_events, get_catalog, run_report, compare_periods. There is no mixing of casing or verb styles.

Tool Count5/5

Five tools is lean but appropriate for a read-only reporting integration: app discovery, event discovery, catalog lookup, report execution, and period comparison. Each tool has a distinct role and none feels redundant.

Completeness4/5

The set covers the core read-only workflows: discovering apps, discovering events and metrics, reading catalog metadata, running reports, and comparing periods. Minor gaps may exist around saved reports or broader filter/dimension enumeration, but the surface is largely complete for reporting.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues