Hello,
I would like to thank you for making umami + AI agentic context as easy as possible, I have used umami-mcp today to create such analytical reports for the analytic data that I have collected, remarkable.
On the other hand, it was hard for me to understand, why TEAM_ID is environmental variable, up to the modulare structure umami provides, I believe it should be a dynamic parameter that you give in agentic context that "get_teams" should work to obtain which teams that user is added to collect analytics for and user should orchestrate prompt engineering accordingly.
It is just my ideal concept of the expectation and matching "umami" approach to provide teams+users for access management.
Thanks again for your support, appreciated to make use of umami-mcp!
Hello,
I would like to thank you for making umami + AI agentic context as easy as possible, I have used umami-mcp today to create such analytical reports for the analytic data that I have collected, remarkable.
On the other hand, it was hard for me to understand, why TEAM_ID is environmental variable, up to the modulare structure umami provides, I believe it should be a dynamic parameter that you give in agentic context that "get_teams" should work to obtain which teams that user is added to collect analytics for and user should orchestrate prompt engineering accordingly.
It is just my ideal concept of the expectation and matching "umami" approach to provide teams+users for access management.
Thanks again for your support, appreciated to make use of umami-mcp!