
Firstlytics
io.github.firstlytics由 GitHub 账号 firstlytics 发布v1.0.0更新于 Nov 14, 2026
Your Firstlytics web and product analytics: reports, goals, funnels, users and custom SQL.
概览
将助手接入 Firstlytics 网站与产品分析,可查询报表、漏斗、目标、用户及自定义 SQL。
- 可以做什么
- 列出站点,读取或修改站点设置
- 读取流量报表:概览、时间序列、细分、实时访客、访问与事件
- 查看 JS 错误、Core Web Vitals、路径、注释与分群
- 管理漏斗与目标,含转化与流失分析
- 查询登录用户、用户特征、留存、活跃用户与功能使用
- 运行自定义 SQL,读取 Search Console 数据
- 适用场景
- 适合让助手直接回答关于自有站点流量与产品使用情况的问题,例如注册来源,并在不打开后台的情况下维护目标、漏斗和分群。
- 运行要求
- 可使用 Streamable HTTP 的托管端点并携带 Authorization bearer 头,或使用 npm 包在本地以 stdio 运行,需 Node.js 20 或更高版本。两者都需要在组织设置中创建的 API 密钥,通过 FIRSTLYTICS_API_KEY 或 Authorization 头提供;密钥的作用域决定可用工具。自定义 SQL 需要 Scale 套餐。
安装
在 SourceWeft 中
- 打开 控制台中的 Firstlytics,将其添加到工作区。
- 连接 Authorization token 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.firstlytics%2Fmcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"firstlytics": {
"type": "http",
"url": "https://api.firstlytics.com/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
Firstlytics MCP server
Firstlytics is first-party web and product analytics: cookieless by default, with the tracker on your own domain. This is its Model Context Protocol server: Claude, Cursor and other AI assistants can answer questions such as "Where did last week's signups come from?" with your data, and manage your goals and funnels.
There are two ways to connect, with the same tools:
- Hosted, at
https://api.firstlytics.com/v1/mcp(Streamable HTTP), for clients that connect to remote servers: Claude Code, Cursor, VS Code, Windsurf and others. Nothing to install. - This package,
@firstlytics/mcp, over stdio, for clients that start local servers, such as Claude Desktop:npx -y @firstlytics/mcp. It is a bridge to the hosted server, so its tools are always the hosted server's.
Both sign in with an organisation API key.
The API key
In Firstlytics, Organization settings → API keys → New key. The key's scopes decide what the assistant can do, and a key limited to some sites sees only those:
For an assistant that only reads reports, give it stats:read and sites:read. Add the write scopes only when
you want it to change things; it asks before deleting anything.
Set it up
Replace fl_live_... with your key.
Claude Code
Claude Desktop
Settings → Developer → Edit Config, then in claude_desktop_config.json:
Restart Claude Desktop after saving. It needs Node.js 20 or later.
Cursor
In ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):
VS Code
In .vscode/mcp.json; VS Code asks for the key the first time and keeps it:
Other clients
A client that connects to remote servers: https://api.firstlytics.com/v1/mcp, Streamable HTTP, with the header
Authorization: Bearer fl_live_....
A client that starts local servers: the command npx -y @firstlytics/mcp, with FIRSTLYTICS_API_KEY in its
environment.
Tools
Every tool does what the matching API endpoint does, with the same checks. The user tools read data collected with cookies, so they need a site in a cookie mode; on a cookieless site they find no users.
The full guide: firstlytics.com/docs/settings/mcp-server.
Configuration
Good to know
- The assistant reads what your visitors left in your data: page titles, paths, referrers, event names. Treat what it suggests from them as you would any text from the web.
- Delete a key in Organization settings when you no longer use it; the assistant loses access at once.
- The key is sent only to the server in
FIRSTLYTICS_MCP_URL, over HTTPS. This package keeps nothing on disk.
Development
The tests run the bridge against a stand-in for the hosted server, in memory and as the firstlytics-mcp
command over stdio.
Questions and bugs: GitHub issues or [email protected].
License
MIT, © FunFirst s.r.o.
来源:README.md,提交 70fd7f0
工具
0版本历史
1- v1.0.0最新Nov 14, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分