> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/mcp/mcp-how-it-works.md).

# How it works

Your AI client connects to the MCP Server, which acts as a secure bridge to the Public API. When you ask a question, the AI translates your request into the appropriate API calls, retrieves the data, and presents the results in a clear, readable format.

```
Your AI assistant ──▶ mcp.<ad-network-domain>/mcp ──▶ api.<ad-network-domain>/v2 ──▶ Your data
```

All requests go through the same permission system as the platform's API: you can only access the data you are authorized to see. On top of that, every call is checked against the access levels chosen for that connection, before the API is reached. Because the server sits behind the platform's own domain and admin panel, the white-label boundary is preserved end to end.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.exads.com/mcp/mcp-how-it-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.