Full MCP support
Connect compatible AI clients to public product knowledge or authenticated operational deployments. Select the server and domain, inspect sessions and question history, and use the tools available to your identity. Privileged actions follow the connected server’s permissions and operating policy.
POST /mcp
→ initialize
← capabilities: tools, resources, prompts
→ tools/list
← get_nexus_overview
← get_product_capabilities
← get_targeting_controls
← get_ad_format_guide
← get_operating_capabilities
← recommend_deployment
← get_security_modelPublic discovery / no account access
Read product capabilities, formats and deployment guidance through typed MCP tools, resources and prompts. The public endpoint cannot access your private platforms or change their data.
Explore public tools ↓Connected operations / authenticated
Authorize an AI client against the operational deployment. Select the relevant domain and inspect the tools it exposes. Administrators can review activity, diagnostics and approval history where the server supports them.
Plan an operational connection ↗Inside Nexus / AI + MCP
Nexus includes a personal MCP setup screen and a guided operations interface for the resources available to the current account. These are separate from the public website’s product-information assistant.
Review the connection identity, Streamable HTTP endpoint and credential-handling guidance before authorizing an AI client.
The guided resource picker covers campaigns, Search, XML, RTB, Video, CPA and publisher operations within the current role and module access.
Captured from Nexus. Identifying details are hidden. The account name and endpoint are hidden. The operations capture shows resource selection only; no AI connection, command or data change was executed for these screenshots.
A new interface to AdTech
The assistant and MCP server use the same curated Nexus product model. The website helps buyers understand the platform; MCP lets AI clients discover that knowledge through typed tools and resources instead of scraping pages.
The operational workspace
Connect the MCP servers your business operates. The administration workspace exposes the capabilities each server supports, organized by deployment and domain—not mixed into one untraceable stream.
Register separate MCP deployments and select the server and domain before reviewing its operational context. Keep production and test environments distinct.
Review session activity, question history, tool outcomes and latency. Inspect the evidence behind an interaction instead of relying on the final chat answer alone.
Use the connected server’s approval, automation and audit capabilities. An AI request never replaces the server’s access checks or the deployment’s operating policy.
Inspect learning proposals, supporting evidence and review outcomes where the remote server exposes them. Keep changes to operational guidance visible to administrators.
get_nexus_overviewDiscover the platform, AdTech engineering heritage, revenue engines and AI-native operating model.
get_product_capabilitiesInspect typed capabilities for Search, feeds, OpenRTB, video or CPA.
get_targeting_controlsCompare geographic, device, domain, sub-ID, filtering and traffic-limit controls across supported channels.
get_ad_format_guideExplain what an ad looks like, where it appears, how it is bought, targeted, delivered and measured.
get_operating_capabilitiesResearch traffic quality, feed and bid policy, partner operations, direct campaigns, contextual monetization and custom engineering.
recommend_deploymentMap a business model and channel mix to a phased Nexus deployment.
get_security_modelUnderstand authentication, authorization and infrastructure boundaries.
Example questions
recommend_deploymentWhich Nexus product fits an ad network?
Start with the channels already carrying revenue, map partner access and traffic policy, then phase Search, feeds, OpenRTB, video or CPA into one tenant-aware control plane.
Illustrative product answer · no customer data · no write operationHow AI clients connect
The AI client connects to the Nexus Streamable HTTP endpoint and negotiates MCP capabilities.
It lists typed tools, reads the product catalog resource and can use the solution-discovery prompt.
The client combines published Nexus product information with the customer’s business question.
Public tools are read-only. Connected operational servers expose privileged tools behind scoped authentication, deployment policy and approval requirements.
Open by design
Compatibility depends on the client supporting the Nexus Streamable HTTP transport and its authentication model. Exact connection instructions are validated per client and deployment.
AI-ready from day one