TrafficOX MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRAFFICOX_API_KEY | Yes | Your TrafficOX API key. API access must be enabled for your account. | |
| TRAFFICOX_API_URL | No | The TrafficOX API base URL. | https://api.trafficox.com/api |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountB | Current TrafficOX account: email, name, balance (USD). |
| get_balance_statsB | Daily earned/spent (USD) for the account plus totals and current balance. |
| get_filter_valuesA | Valid values for stats filters: countries, categories, desktop/mobile OS, desktop/mobile browsers, platform. Call this before filtering if unsure of exact spelling. |
| list_ordersC | All buy orders (campaigns) or sell orders (placements) of the account for one ad format. |
| get_orderB | Full order details. Buy orders include targeting (order_filter), traffic filter and the attached domain filter. |
| get_order_statsA | Statistics of one buy or sell order grouped by a dimension. Buy rows: hits, unique, desktop, mobile, spent, cpm, conversions, cost_per_conversion, conversion_rate, conversion_revenue, winrate, profit. Sell rows: total, unique, sold, sent_back, earned, cpm. group_by=sub_id is sell-only; group_by=domain is not available for sticker sell orders. subdimension adds a nested |
| get_sub_id_reportA | Sell-order earnings grouped by up to three sub-ID levels (sub_id_1..3), cursor-paginated: pass the returned |
| list_rtb_feedsA | RTB demand feeds (DSP endpoints) of the account for one format, with state. |
| get_rtb_feedC | One RTB demand feed with its settings. |
| get_rtb_statsA | RTB statistics grouped by a dimension — for the whole account, or for one feed when feed_id is given. Terms groupings return 10 rows unless |
| list_domain_filtersC | Domain blacklists/whitelists of the account, 20 per page. |
| get_domain_filterC | One domain filter with its full domain list. |
| list_conversion_trackersC | S2S conversion trackers of the account. |
| get_conversion_trackerC | One conversion tracker with its postback settings. |
| list_conversion_eventsC | Conversion postbacks received by a tracker, newest first, paginated. |
| set_buy_order_stateA | Start (active) or pause (paused) a popunder buy order. Starting it resumes buying traffic and spending balance. |
| set_rtb_feed_stateA | Start (active) or pause (paused) an RTB demand feed; bidding changes within ~10 seconds. Account managers are notified. |
| create_domain_filterA | Create a domain blacklist or whitelist. Invalid domains are skipped and listed in |
| add_domains_to_filterA | Append domains to a domain filter (max 15,000 per filter). Invalid domains are skipped and listed in |
| remove_domains_from_filterA | Remove domains from a domain filter. Takes effect on every order using this filter. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools target clearly distinct resources or actions, such as orders vs RTB feeds vs domain filters. There is some conceptual overlap among the stats tools (get_order_stats, get_sub_id_report, get_rtb_stats), but the descriptions clarify their different scopes and grouping options.
Every tool follows a consistent snake_case verb_noun pattern: get_, list_, set_, create_, add_, remove_. There are no mixed casing styles or vague one-word tool names.
The server exposes 20 tools for a fairly broad ad-traffic domain, which is on the heavy side for an MCP toolset. While most tools map to distinct operations across account, stats, orders, filters, trackers, and RTB feeds, the surface feels larger than necessary rather than tightly scoped.
Core read, stats, domain-filter CRUD, and some state toggles are present, but there are notable gaps: no create/update operations for buy/sell orders, conversion trackers, or RTB feeds. Order state changes only cover popunder buy orders, leaving broader order lifecycle management incomplete.