A compatible client connects to the public MCP endpoint, initializes a protocol session and discovers the tools, resources and prompts advertised by the server.
Connection endpoint
The Nexus MCP endpoint is available at /mcp and uses Streamable HTTP. Production clients should use the canonical HTTPS domain.
- Initialize
- List capabilities
- Call approved tool
- Read structured result
Discovery before action
Clients should inspect tool schemas rather than guessing parameter names or scraping button labels from the website.
Bounded capability
Current public MCP operations focus on product understanding and solution design. Operational write actions should require separate authentication and authorization before they are introduced.
This guide describes Nexus product architecture and general AdTech operating concepts. Exact enforcement and integration behavior depends on the enabled revenue engine and agreed deployment configuration.