Ask an assistant about your own numbers.
Skomi speaks the Model Context Protocol, so an assistant you already use can read your traffic and answer in words. Point it at one URL, give it a key, and ask. Nothing to install, and nothing it can change.
The questions it is good at
Anything the dashboard can show, without opening it. Also the follow-up question, which is usually the part that takes five clicks.
- "Which pages lost traffic this month compared with last?"
- "Is the new app release crashing more than the previous one?"
- "Where did mobile visitors from Germany land, and did they bounce?"
- "Summarise last week for every site I own."
The last one is the reason account-wide keys exist. An assistant with a key for one site can only ever answer about that site.
The whole setup
One entry in your client's MCP configuration. It is the same block for Claude Code, Claude Desktop and Cursor. Only the file it goes in differs.
{
"mcpServers": {
"skomi": {
"type": "http",
"url": "https://mcp.skomi.com/mcp",
"headers": { "Authorization": "Bearer YOUR_SKOMI_API_TOKEN" }
}
}
} Where the key comes from
Skomi → Settings → API access mints a key for every site and app you own. A site's or app's own API access tab mints one for just that one. The secret is shown once, when you create it.
An account-wide key reads everything you own, so treat it like a password. A per-site key costs one site if it leaks, so prefer it when a tool only needs one. Either can be revoked, and revoking takes effect on the next request.
With an account-wide key, ask it to list your sites first. It needs an id before it can read anything, and it cannot guess one.
What it will not do
It only reads
Every tool is read-only, because the API behind them is. There is no request an assistant can make through this that changes a site, an app, a setting or a number.
We never hold your key
Your client sends the key with each request and the server forwards it. Skomi's MCP server stores no credential of its own, so it can reach nothing you could not already reach with curl.
Only what you own
A site somebody shared with you is deliberately out of reach. Reading it through your key would re-share their data through a credential they cannot see or revoke.
You can see it working
Every key lists when it was created and when it was last used, next to a button that revokes it.
It reads what you are already collecting.
If you have a site in Skomi, the key is two clicks away and the configuration is the block above.