Skip to content

t1k:ads-mcp:mintegral

FieldValue
Modulemonetization
Version1.4.26
Efforthigh
Tools—
/t1k:ads-mcp:mintegral

@theonekit/mintegral-mcp-server — 17 tools (6 read, 11 guarded write). Mintegral is one network with two sides, and this one package serves both: the advertiser / UA API (offers, bids, budgets, campaign reports) and the publisher / monetization API (apps, placements, units, publisher reports).

  • Reading or editing Mintegral offers, bids, budgets (advertiser side)
  • Pulling a campaign report or a publisher report
  • Creating or editing apps, placements, ad units (publisher side)
  • Diagnosing Mintegral auth failures — the three-host split below is the usual cause
  • Interpreting offer output that shows a goal instead of a bid

Auth — three hosts, three credential pairs

Section titled “Auth — three hosts, three credential pairs”

Mintegral signs with MD5 (not HMAC) and passes auth as query parameters (not headers):

sign = md5(secret + md5(timestamp)) // timestamp = Unix seconds

The APIs are split across three hosts, each with its own credential pair — do not reuse one pair across hosts:

DomainHostAuth paramsEnv vars
Advertiser / UAss-api.mintegral.comaccess-key, token, timestamp (HTTP headers)MINTEGRAL_ADV_USERNAME, MINTEGRAL_ADV_API_KEY
Publisher reportingapi.mintegral.comskey, time, signMINTEGRAL_PUB_SKEY, MINTEGRAL_PUB_SECRET
Developer / listing + dev writesdev.mintegral.comskey, time, signMINTEGRAL_DEV_SKEY, MINTEGRAL_DEV_SECRET

The advertiser host derives its token differently: token = md5(api_key + md5(timestamp)).

Credentials are validated lazily, per tool call. An operator holding only one side’s credentials can still use that side’s tools — a missing pair fails only the tools that need it, not the server.

Both must be on before anything mutates:

  1. MINTEGRAL_ALLOW_WRITES=1 (env). Unset or not 1, every write tool only ever previews — it returns the diff/payload it would send — even when called with confirm:true.
  2. confirm: true (per call). Every write tool defaults to confirm:false, i.e. preview.

Additional guards: advertiser offer-writes refuse account-managed offers (maintain_by != "ADV"), and updates re-check for drift before executing.

Preview output is the normal way to work here — read the previewed payload before flipping confirm.

Reads (6)

ToolAPIEndpoint
mintegral_list_offersAdvertiserGET /api/open/v1/offers
mintegral_get_campaign_reportAdvertiserGET /api/v1/reports/data
mintegral_list_placementsDeveloperGET /v2/placement/open_api_list
mintegral_get_publisher_reportPublisherGET /reporting/v2/data
mintegral_list_appsDeveloperGET /v2/app/open_api_list
mintegral_list_unitsDeveloperGET /v2/unit/open_api_list

Advertiser writes (5, guarded) — create_offer, update_offer (incl. ad schedule), set_offer_status (start/pause), update_bid (default/geo/mtgid), update_budget.

Publisher / Developer writes (6, guarded) — create_app, create_placement, create_unit, update_unit (target eCPM / eCPM floor), update_placement, update_app.

Terminal window
bun run --filter @theonekit/mintegral-mcp-server build
bun run --filter @theonekit/mintegral-mcp-server test

Tests are fully mocked — no live API. Signing is verified against Mintegral’s published golden vector, formatters against verbatim doc samples, and write tools through dependency-injected stub clients (kill-switch, drift, maintain_by, encoding).