Full MCP support · Free external integration
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_public_knowledge
← get_targeting_controls
← get_ad_format_guide
← get_operating_capabilities
← recommend_deployment
← get_security_modelChatGPT and other compatible AI clients
$0Nexus integration fee
Connect your Nexus platform to ChatGPT and other compatible MCP clients with no Nexus integration fee. The paid in-platform AI add-on is not required.
Prefer AI inside Nexus? $500/month per platform, with model usage included and 1 month free from activation.
Third-party AI client subscriptions and AI provider fees are not included and may apply separately. Connection availability depends on your client, account and workspace settings; platform access still requires authorization.
Public 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 the operation
Choose a stage to see its controls. This is a workflow explanation; explore the actual platform in a demo.
Register separate MCP deployments and select the server and domain before reviewing its operational context. Keep production and test environments distinct.
Bring your operating requirements. We will walk through the current interface and the relevant configuration, integrations and reporting controls.
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_public_knowledgeFind sourced product facts, published capacity prices and engineering services. Filter by topic and read the same evidence used by the website assistant, including add-ons and billing rules.
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