> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/faq/marketing-optimization/connect-manus-ai-to-the-data-assistant.md). # Connect Manus AI to the Data Assistant Want to use Manus AI to analyze your tracking data autonomously? Connect Manus to your AdPage account in minutes through the AdPage MCP server. Manus can then query your GA4, Google Ads, Meta Ads, Tik *** ### What is the AdPage × Manus integration? [Manus](https://manus.im/) is an autonomous AI agent. It answers questions and **performs tasks** independently. It can build reports, identify anomalies, run attribution analyses, and return results in a document, spreadsheet, or presentation. Add the AdPage MCP server as a **Custom MCP connector** in Manus. The agent then gets direct access to the same tools as the Data Assistant: * Server-side tracking data from ClickHouse, including outgoing and incoming requests and webhook logs * GA4, Google Ads, Meta Ads, TikTok, and LinkedIn data * Magento and Shopify data, including orders, inventory, and marketing * Attribution reports, funnels, and data quality checks * GTM container audits and consent mode validation > 💡 **Difference from Claude MCP:** With Claude, you ask a question and receive an answer. Manus completes an entire workflow. For example, ask it to create a weekly performance report for your Magento store. It returns the completed document. *** ### What do you need? Before you start, make sure you have: * An active **AdPage account** with at least one container * Access to the AdPage platform * A **Manus account**, free or paid — register at [manus.im](https://manus.im/) * Five minutes > ⚠️ **Important — token = password:** The MCP URL includes a personal token. It lets Manus retrieve data from your AdPage account. Never share this URL with others. Do not commit it to Git or public files. *** ### Step 1: Get your MCP URL in AdPage Open your AdPage account and copy your personal MCP URL. 1. Sign in at [data.adpage.io](http://data.adpage.io/). 2. Select **Integrations** in the left menu. 3. Scroll to **Account integrations**. 4. Select the **Manus AI** card. [![](https://euw1.frontkb-cdn.com/attachments/9808087/547522/9922377b-ff52-4e6b-a5e2-90e301820949.png)](https://euw1.frontkb-cdn.com/attachments/9808087/547522/9922377b-ff52-4e6b-a5e2-90e301820949.png) 5. In the popover, select the orange **Copy** button beside the URL field. [![](https://euw1.frontkb-cdn.com/attachments/9808087/547522/3cc1d75d-0463-490f-aad4-df9c3eb60f9f.png)](https://euw1.frontkb-cdn.com/attachments/9808087/547522/3cc1d75d-0463-490f-aad4-df9c3eb60f9f.png) Your MCP URL has this format: ```bash https://mcp.adpage.io/mcp?token=gtmuser-xxxxxxxxxx ``` > 🔄 **Need a new token?** Select **Renew token** in the same popover. This immediately invalidates your old token. Use this if you suspect it has leaked. Update the URL in Manus afterwards. *** ### Step 2: Open Connectors in Manus 1. Open [manus.im](https://manus.im/) and sign in. 2. Select your **profile picture** in the bottom left. 3. Select **Connectors** in the sidebar. 4. Select the **+ Add connectors** tile. Show image [![](https://euw1.frontkb-cdn.com/attachments/9808087/547522/f78defac-5b80-4e32-a138-a937acce1c0a.png)](https://euw1.frontkb-cdn.com/attachments/9808087/547522/f78defac-5b80-4e32-a138-a937acce1c0a.png) *** ### Step 3: Add a custom MCP server 1. Select the **Custom MCP** tab at the top. 2. Select **+ Add custom MCP server**. [![](https://euw1.frontkb-cdn.com/attachments/9808087/547522/889b8a2b-1b2c-476c-8fd1-29bb5a629436.png)](https://euw1.frontkb-cdn.com/attachments/9808087/547522/889b8a2b-1b2c-476c-8fd1-29bb5a629436.png) 3. Select **Direct configuration** from the dropdown menu. > 💡 **Why Direct configuration?** This option lets you enter each field separately. It is easier than preparing a JSON block. It also gives you more control over the name and extra headers. *** ### Step 4: Enter the MCP configuration Enter the connector details. Copy the values in this table exactly. [![](https://euw1.frontkb-cdn.com/attachments/9808087/547522/336c2d6c-9d0a-46b2-9ad9-7e6dc45c0d99.png)](https://euw1.frontkb-cdn.com/attachments/9808087/547522/336c2d6c-9d0a-46b2-9ad9-7e6dc45c0d99.png) | Field | Value | Description | | --------------------- | ----------------------------------- | ------------------------------------------------------------------------------ | | **Server Name** | `AdPage MCP` | Choose any recognizable name, such as `AdPage MCP` or `AdPage – {client name}` | | **Transport Type** | `HTTP` | Required. AdPage MCP uses standard HTTP transport | | **Icon** *(optional)* | `https://www.adpage.io/favicon.ico` | Makes the connector easier to recognize in your connector list | | **Note** *(optional)* | See the suggestion below | Helps Manus understand when to use this MCP | | **Server URL** | Paste your copied URL | The URL from Step 1, including `?token=...` | | **Custom headers** | Leave empty | Not needed. Authentication is already included in the URL token | #### Recommended text for the Note field Manus uses the Note field to decide when to use this MCP server. Enter a short instruction, such as: ```kotlin Use this MCP for all questions about server-side tracking data, GA4, Google Ads, Meta Ads, TikTok, LinkedIn, Magento, and Shopify performance. It includes data quality checks, attribution reports, funnels, GTM audits, and consent mode validation. Use 'list_containers' to show available containers. Always choose a container before running a query. ``` 5. Select **Save** in the bottom right. *** ### Step 5: Test the connection After saving, `AdPage MCP` appears with a green checkmark in your Custom MCP list. Test the connection. 1. Open a **new chat** in Manus. 2. Ask a simple question, such as: > *Which containers are available in my AdPage account?* 3. Manus should call `list_containers` and return your containers. Does it work? Try a more complex request: > *Create an Excel report for my Google Ads campaigns from the past 30 days. Include cost, conversions, and ROAS per campaign. Compare these results with the preceding 30 days.* Manus now independently chooses a container → retrieves Google Ads data → compares the figures → creates an Excel file → returns it in the chat. *** ### Common issues #### “MCP server unreachable” or a red error when saving Check the following: * Is the **Server URL** complete, including the `?token=...` portion? * Is **Transport Type** set to `HTTP`, rather than `SSE` or `WebSocket`? * Does the URL contain no extra spaces or line breaks? #### “Unauthorized” or “Invalid token” when running a query Your token has expired or was renewed manually. Return to **Integrations → Manus AI** in AdPage. Select **Renew token**. Then paste the new URL in Manus through *Connectors → AdPage MCP → Edit*. #### Manus does not use AdPage MCP automatically The agent partly selects tools based on the **Note** you entered. If it does not work automatically, enter a more detailed note. You can also explicitly mention AdPage in your prompt: > *Use the AdPage MCP to …* #### I do not see container integrations in the results AdPage MCP only provides data from integrations connected to your AdPage container. In **Integrations → Container integrations**, check that the relevant platforms are active for the selected container. These platforms include Google Analytics, Google Ads, Meta Ads, TikTok, LinkedIn, Magento, and Shopify. *** ### Security and best practices * **Treat the MCP URL as a password.** Store it in a password manager, such as 1Password or Bitwarden. Never share it by email or chat. * **Use separate tokens for each employee.** Each person can retrieve their own MCP URL through their AdPage account. This keeps audit logs traceable by user. * **Revoke tokens during offboarding.** When an employee leaves, select **Renew token**. Their old URL will no longer work. * **The MCP is mostly read-only.** Manus cannot modify GTM containers through MCP. This changes only if you explicitly enable write permissions in AdPage. --- # 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.adpage.io/faq/marketing-optimization/connect-manus-ai-to-the-data-assistant.md?ask=&goal= ``` `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.