Appearance
Available MCP tools
Nexus advertises only the tools allowed for the authenticated member, tenant, enabled modules, OAuth scopes, ownership, and /mcp endpoint.
Ask in natural language. The client should select tools automatically, but the names below make behavior and safety easier to verify.
Start every workflow here
| Tool | Purpose |
|---|---|
nexus_whoami | Show identity type, tenant, modules, OAuth scopes, and visible capability counts |
nexus_help | Search role-visible workflows, entities, enums, and operations in natural language |
nexus_resolve_command | Resolve one Bulgarian/English request to a canonical target and safe next tool |
nexus_plan_commands | Split several independent requests into an ordered durable plan without changing Nexus data |
Example:
Show who I am in Nexus, which modules and scopes I have, and whether campaign, Search, XML, and advertiser statistics tools are available. Do not change anything.
Complete endpoint catalog
Nexus MCP contains a source-generated catalog for the MCP-safe Nexus backend surface. Generic tools provide coverage when no focused alias exists.
| Tool | Purpose |
|---|---|
nexus_list_endpoints | Search permitted operations by text, method, path, module, or effect |
nexus_describe_endpoint | Show exact method/path, parameters, source, permissions, required scopes, and UI consumers |
nexus_read | Call a permitted catalogued GET operation |
nexus_query | Call a catalogued read-only POST query |
nexus_write | Call an authorized JSON mutation after exact confirmation |
nexus_upload | Perform a permitted CSV multipart operation after confirmation |
HTTP POST does not automatically mean mutation. The generated operation contract marks each operation as read, write, or destructive; a read-only POST must use nexus_query.
Campaign tools
Advertiser members receive focused campaign tools when the live Nexus menu grants advertiser campaign access.
| Tool | Purpose |
|---|---|
nexus_list_campaigns | List/count owned campaigns with filters, sorting, pagination, and optional full details |
nexus_get_campaign | Read one owned campaign's complete advertiser-safe configuration |
nexus_create_campaign | Create a validated campaign after preview and confirmation |
nexus_update_campaign | Update an owned campaign after exact diff and confirmation |
nexus_clone_campaign | Clone an accessible campaign through a confirmed workflow |
nexus_update_campaign_status | Activate, pause, or perform another permitted status transition |
List filters
nexus_list_campaigns supports:
| Input | Examples |
|---|---|
status | active, paused, pending, suspended, scheduled, or numeric status |
campaignIds | [12345, 12346] |
campaignTypes | Nexus campaign type codes returned by nexus_get_enum |
customSearch | Name text or exact numeric CID text |
orderBy | cid, name, website, payout, d_revenue, t_revenue, daily_budget, total_budget |
order | asc or desc |
offset, limit | MCP result window; follow nextOffset until null |
detailLevel | summary or full; full details are capped to a safe 25-row window |
Concrete prompts:
How many active campaigns do I own? Return the exact count and status breakdown.
Find campaigns containing “Summer”, sort by name, and show CID, website, bid, budgets, spend, and status.
Load the full configuration for campaigns 12345 and 12346 and explain their geo, device, schedule, and frequency-cap differences.
Prepare pausing campaign 12345. Show current status, exact payload, expected effect, and verification read. Wait for my confirmation.
The caller never supplies another advertiser UID. Ownership comes from the authenticated Nexus session. A missing and a foreign CID return the same not-found response.
Statistics and reporting
| Tool | Purpose |
|---|---|
nexus_list_statistics_capabilities | List permitted Search/XML/Advertiser table types, groupings, metrics, and KPI rules |
nexus_analyze_statistics | Fetch complete pages, calculate totals/weighted KPIs, rank segments, compare periods, and find anomalies |
nexus_get_advertiser_stats | Focused advertiser reporting |
nexus_get_search_dashboard / nexus_get_search_stats | Search dashboard and detailed statistics |
nexus_get_xml_dashboard / nexus_get_xml_stats | XML dashboard and detailed statistics |
The analysis layer covers campaign/SID/TID, country, OS, browser, device, domain, carrier, connection, keyword, and other role-visible tables. It sums additive fields but recomputes percentages, EPC, RPM, CTR, and other unit economics from their components.
Example prompts:
Analyze advertiser campaign performance from 2026-08-01 to 2026-08-17. Include complete totals, weighted KPIs, top and bottom campaigns, previous-period comparison, anomalies, and data-quality warnings.
Compare Search traffic by country and device for the last two equal 7-day periods. Explain changes using only returned Nexus evidence.
Analyze XML TID 12345 by SubID, rank by net revenue, and flag invalid traffic or incomplete pages.
Search and XML provider tools
| Tool | Purpose |
|---|---|
nexus_list_feed_providers | Find generated Search and XML provider adapters |
nexus_inspect_feed_provider | Show fields, types, options, sensitive markers, URL evidence, and payload placement |
nexus_match_feed_provider | Match a provider name or URL without guessing ambiguous candidates |
nexus_prepare_provider_feed | Load the live form, build/redact payload, report missing data, and prepare approval |
nexus_create_provider_feed | Recheck and create the approved feed with confirm=true |
nexus_diagnose_provider_stats | Run the UI-equivalent API test with update=false and return concrete remediation |
Example prompts:
Match this provider URL to the correct Search or XML adapter. Show extracted field mappings and missing required values, but redact all credentials.
Prepare a new AdKernel XML feed from this URL. Show the provider evidence and final redacted payload; do not create it until I confirm.
Diagnose statistics for XML feed 77 on 2026-08-19. Show health, normalized totals, missing configuration, evidence, and safe fixes. Do not force an update.
Provider diagnostic output never contains a raw provider body, full credential-bearing URL, or configured secret.
Knowledge and safe changes
| Tool | Purpose |
|---|---|
nexus_list_workflows / nexus_get_workflow | Find exact role-visible steps and cautions for a task |
nexus_get_entity_schema | Show backend/UI field types, identifiers, sensitive markers, and evidence |
nexus_get_enum | Return verified campaign status/type/module and other code dictionaries |
nexus_get_operation_contract | Show required fields, conditions, scopes, preflight, and verification |
nexus_get_form_context | Read live create/edit form context with secret-like values redacted |
nexus_prepare_change | Validate and preview a mutation without executing it |
nexus_prepare_controlled_change | Apply policy/DLP checks and issue a payload-bound approval fingerprint |
nexus_change_entity | Resolve a confirmed high-level create/update/clone/delete/bulk action |
nexus_rollback_change | Restore captured update fields only when no later change conflicts |
Required write sequence
- Read the live object.
- Load the workflow, schema/form context, and operation contract.
- Prepare the exact non-secret payload and diff.
- Resolve policy or DLP findings.
- Show the preview to the user.
- Obtain explicit confirmation for that exact payload.
- Execute once with the approval fingerprint and a unique idempotency key.
- Perform the contract's verification read.
The server rejects changed payloads, reused confirmations, insufficient scopes, foreign objects, and outdated authorization.
Multi-command plans
Use nexus_plan_commands when one request contains independent actions:
Pause Search feed 15, activate XML feed 22, and show campaign 45.
Nexus creates three ordered steps. Each mutation has its own preview, confirmation, approval, idempotency, and verification. The read step has no mutation confirmation. Plans are sequential and non-atomic; completed steps are never repeated during a reviewed resume.
Related tools:
nexus_list_command_plansnexus_get_command_plannexus_confirm_plan_stepnexus_execute_plannexus_cancel_command_plan
Scheduled tasks
When OAuth includes offline_access, Nexus can create constrained tenant/user-owned schedules. It never stores arbitrary code or a literal access token.
| Tool | Purpose |
|---|---|
nexus_prepare_scheduled_task | Validate the action/schedule and create an approval fingerprint |
nexus_create_scheduled_task | Store the unchanged approved task |
nexus_list_scheduled_tasks / nexus_get_scheduled_task | Read owned schedules and bounded history |
nexus_pause_scheduled_task / nexus_resume_scheduled_task | Pause or resume future runs |
nexus_cancel_scheduled_task | Permanently stop future runs while keeping audit history |
nexus_run_scheduled_task_now | Run the approved action once without shifting its next schedule |
Supported workflows include campaign status/budget/weekdays, Search/XML feed controls, metric guards, provider health, spend guards, analysis, and weekly reports.
Tool results and errors
Successful backend calls expose text content and structured { status, data }. Tool errors contain an error, HTTP-like status, and optional redacted backend details.
| Status | Typical meaning |
|---|---|
400 | Invalid tool input, contract, or protocol request |
401 | OAuth token missing, expired, revoked, or bound to another resource |
403 | Role, module, scope, ownership, policy, or confirmation denied the action |
404 | Object missing or inaccessible; ownership is not disclosed |
409 | State, idempotency, approval, or concurrent-change conflict |
429 | Rate or quota limit reached |
5xx | Temporary MCP storage, Nexus backend, or upstream provider failure |
Continue with MCP troubleshooting when a connection or tool call fails.