t1k:ads-mcp:mintegral
| Field | Value |
|---|---|
| Module | monetization |
| Version | 1.4.26 |
| Effort | high |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:ads-mcp:mintegralMintegral
Section titled “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).
When to Use
Section titled “When to Use”- 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 secondsThe APIs are split across three hosts, each with its own credential pair — do not reuse one pair across hosts:
| Domain | Host | Auth params | Env vars |
|---|---|---|---|
| Advertiser / UA | ss-api.mintegral.com | access-key, token, timestamp (HTTP headers) | MINTEGRAL_ADV_USERNAME, MINTEGRAL_ADV_API_KEY |
| Publisher reporting | api.mintegral.com | skey, time, sign | MINTEGRAL_PUB_SKEY, MINTEGRAL_PUB_SECRET |
| Developer / listing + dev writes | dev.mintegral.com | skey, time, sign | MINTEGRAL_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.
Writes are gated — two independent keys
Section titled “Writes are gated — two independent keys”Both must be on before anything mutates:
MINTEGRAL_ALLOW_WRITES=1(env). Unset or not1, every write tool only ever previews — it returns the diff/payload it would send — even when called withconfirm:true.confirm: true(per call). Every write tool defaults toconfirm: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)
| Tool | API | Endpoint |
|---|---|---|
mintegral_list_offers | Advertiser | GET /api/open/v1/offers |
mintegral_get_campaign_report | Advertiser | GET /api/v1/reports/data |
mintegral_list_placements | Developer | GET /v2/placement/open_api_list |
mintegral_get_publisher_report | Publisher | GET /reporting/v2/data |
mintegral_list_apps | Developer | GET /v2/app/open_api_list |
mintegral_list_units | Developer | GET /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.
Development
Section titled “Development”bun run --filter @theonekit/mintegral-mcp-server buildbun run --filter @theonekit/mintegral-mcp-server testTests 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).
References
Section titled “References”- Mintegral Advertiser / UA API
- Mintegral Publisher Reporting API
- Mintegral Developer (Create APP & Unit) API
- Package:
packages/mintegral-mcp-server/README.md