Umami MCP server
Umami in any MCP client, through Memtro: Umami does not publish this server. Memtro's Umami connector reads Umami through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Read-only Umami web analytics: visitors, pageviews, visits and bounce rate for a date range, top pages, referrers, countries, browsers, devices and custom events, trends by hour, day or month, and who is on the site right now. Works with Umami Cloud and self-hosted instances.
Reads
umami_websitesList the websites this Umami connection can report on, with the id the other tools take, the domain and when it was added.umami_statsTotals for one website over a date range: pageviews, visitors (unique people), visits (sessions), bounces with the rate…umami_metricsThe top values of one breakdown for a website over a date range, largest first — which pages, where the traffic came from, which countries, browsers…umami_timeseriesPageviews and sessions for a website bucketed by hour, day or month, oldest first…umami_activeHow many people are on a website right now (active in the last five minutes).
Connect it
First connect Umami on Dashboard → Connections, then add Memtro to your client once. The Umami tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
One command registers the server; the tools are then available in every session.
claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
--header "Authorization: Bearer sk-memtro-..."Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Umami connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › How many visitors did we get last week compared with the week before?
- › What are the top 10 pages this month, and which referrers sent the most people?
- › Which countries is our traffic coming from in the last 30 days?
- › Plot pageviews per day for the last month and tell me which day was the outlier
- › How many people are on the site right now?
Questions
- Is this an official Umami MCP server?
- No. It is Memtro's MCP server with Memtro's Umami connector behind it: the connector reads Umami through its API with the credentials you connect on Dashboard → Connections, and Umami publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Umami?
- Not yet. Today every Umami tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.