The Model Context Protocol (MCP) is a new standard for connecting LLMs to any tool, e.g. Figma, Wordpress, Stape, Zapier and many more.
If Piwik would offer an MCP server, clients could easily connect without IT support. A good example of how Piwik could implement this is shown by Zapiers MCP support. You can see it in the blog article “Zapier MCP: Easily connect AI tools with 7,000 apps – without API development”
Benefits and use cases for an MCP server for Piwik Pro:
Make changes to tags via AI chat
Get analytics data via AI chat
Automate tag audits and documentation
Automate tag migrations to hundreds of tags
Though still experimental and bleeding-edge, in the near future it would revolutionize the way, web analytics can be made more efficient. Especially for Piwik PRO enterprise accounts with many tags.
Showcase:
The most popular talk in this years analytics conferences by Gunnar Griese showed, how this would speed up work. His blog article: MCP Servers in Digital Analytics
has videos that show how to setup in the GA4/GTM-stack. It would be really cool, to have this feature in Piwik PRO too!
Thank you for your feedback and kind words. We are already working on an MCP server. Due to the holiday season, there’s a slight slowdown, so I’ll probably post an update here in August. In my opinion, what makes Piwik PRO unique is the sheer number of modules it contains. This gives us a wide range of APIs to cover to provide the base value.
I was setting up the PiwikPro MCP server to power analytics queries in our Claude-Cowork where we have our own organizational plugin. It would work well for individual technical use, I could use it myself, but I’ve hit a wall trying to roll it out to the wider team, and I wanted to share the specific blocker…
The problem: Apparently, and correct me if wrong, Claude has detected that your current MCP implementation is stdio-based, which means it runs as a local process on each user’s machine. This requires uvx to be installed locally, a per-user .env file with API credentials, and a local path hardcoded in the MCP config. For non-technical team members using tools like Claude Cowork, none of this is manageable … there’s no way for them to configure or override MCP server arguments, and asking them to install package managers and create credential files isn’t realistic.
What would make this work for teams: An HTTP-based MCP endpoint hosted by PiwikPro (similar to what Storyblok has done with mcp.labs.storyblok.com). This would allow users to authenticate with their own PiwikPro account credentials via a Connect flow in Cowork … no local setup required, per-user accountability preserved in PiwikPro’s activity logs.
Thank you for sharing the problem. You are correct that our MCP server is currently a local installation that requires setup on your machine. I understand that this can be challenging for non-technical users. The local MCP is our first milestone, and in the future, we may implement a remote server. Integrating with user accounts is more complex, so we decided to release the local version first and plan for the remote version later. At this time, I cannot provide a release date for the remote server.