> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/datalogz-mcp-servers/mcp-server-for-analytics-opps-teams.md).

# MCP Server for Analytics opps Teams

Analytics ops teams who already run Control Tower can now get their answers without interacting with the web interface.

The data is already there. What may not be that obvious in the UI is how to reach it: open the app, pick the connector, filter the Inventory table, export, reconcile, paste into the doc you were writing. The Control Tower MCP server simplifies this. You ask in the window you are already working in, and the governed answer comes back with the assets behind it.

| What you used to do                                                                          | What you ask now                                                                                  |
| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Filter the Inventory table by source type, export to CSV, count the rows                     | *How many semantic models sit on Snowflake?*                                                      |
| Open Alerts, set a date filter, then check the connector list and monitor catalog separately | *Summarize 17 August: alerts, refresh failures, new assets, connectors and monitors*              |
| Open the similarity cluster map, note the candidates, then check usage and lineage per asset | *Rank our reports by near-duplicate count, then show usage and downstream impact for the top one* |
| Filter the Inventory on Users and open the asset page of the user you want to investigate.   | *What does Jordan own, and which workspaces can they reach?*                                      |
| Screenshot BI360 and hope nobody asks where the number came from                             | *Where does the asset count on our executive summary come from?*                                  |

None of this replaces the app. It replaces the trip to the app when what you needed was one number and the list behind it.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.datalogz.io/guides/datalogz-mcp-servers/mcp-server-for-analytics-opps-teams.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.