能做什么
Ask an assistant about your website traffic. Privacy-first web analytics, no cookies. OAuth.
作者提供的原文
- 连接方式 在云端运行
- 账号或密钥 连接时登录该服务(OAuth)
- 分类 营销与社交媒体
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 7/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 27/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Feasible Analytics。按照 https://mcp.popnx.com/i/feasible-analytics-feasible.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(app.feasible.lol) · ✓ 命令已检查 2026年11月19日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称Feasible AnalyticsRemote MCP server URL · 地址https://app.feasible.lol/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsFeasible Analytics
试一试
用 Feasible Analytics 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Feasible Analytics,或回答中出现 Feasible Analytics 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称Feasible AnalyticsConnection · 地址https://app.feasible.lol/mcp在聊天中选择 Feasible Analytics
开启新聊天,输入前先从插件列表中选择 Feasible Analytics
试一试
用 Feasible Analytics 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Feasible Analytics,或回答中出现 Feasible Analytics 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user feasible https://app.feasible.lol/mcp在 Claude Code 中输入 /mcp
应能看到 Feasible Analytics 在列表中并显示已连接
试一试
用 Feasible Analytics 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Feasible Analytics,或回答中出现 Feasible Analytics 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 Feasible Analytics 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Feasible Analytics,或回答中出现 Feasible Analytics 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 Feasible Analytics 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Feasible Analytics,或回答中出现 Feasible Analytics 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://app.feasible.lol/mcpJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user feasible https://app.feasible.lol/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"feasible": {
"url": "https://app.feasible.lol/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"feasible": {
"type": "http",
"url": "https://app.feasible.lol/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
它能做什么
服务器要求先登录,才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Feasible-Analytics 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于昨天
- ✓ 通过
有许可证
使用 AGPL-3.0
- ✓ 通过
端点有响应
在 841 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
云端地址最近 3 次检查中有 3 次响应 · 最近一次 841 ms · 检查于 2026年11月20日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/feasible-analytics-feasible)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“营销与社交媒体”中的其他服务器比较i
- 星标数多于此分类中其他 4243 个服务器的 93%
- 发布到注册中心的时间比此分类中其他 4243 个服务器的 87% 更新
- 基础检查结果等于或优于此分类中其他 4243 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Feasible Analytics 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于昨天,最新版本(1.0.1)于4天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Relaticle
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
ChatbotX
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
X (Twitter) MCP Server by Xquik
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Betterlytics
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
| 本项 Feasible Analytics | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 是 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | AGPL-3.0 | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
feasible.lol
Privacy-first web analytics. One Go binary. One SQLite database per account.
No cookies, no consent banner, and visitor IP addresses are never written to disk. Run it yourself for free, or let us host it for $99 a year.
Status
Live in production at app.feasible.lol. The hosted service runs this code, and the self-hosted build is the same binary with every feature in it.
It's ready for real sites, hosted or on your own server. Releases are still numbered 0.0.x and ship often. Migrations never run on their own, so run feasible db migrate after every upgrade.
Try it
- Live demo, no sign-up: app.feasible.lol/public/stopoverpayingforanalytics.com. The traffic is generated, so click anything.
- Hosted: sign up for a 30-day free trial. No card. After that it's $9.99 a month or $99 a year for unlimited sites, unlimited teammates and 1,000,000 pageviews and events a month across all of them. Going over never stops collection or adds a charge.
- Self-hosted: free, below.
Self-host
Download the archive for your platform from the latest release. There are builds for Linux, macOS and Windows, on amd64 and arm64.
tar -xzf feasible_*_linux_amd64.tar.gz
./feasible --version
Or build it from source with Go 1.26 or newer. The compiled dashboard and tracker are committed, so Node is only needed if you change them.
go build -o feasible ./cmd/feasible
Write the minimum configuration to a file, with your own hostname and email. The salt is generated once here and has to stay the same afterwards, because it's part of how visitors are counted each day.
cat > feasible.env <<EOF
FEASIBLE_ENV=production FEASIBLE_APP_HOSTED=false FEASIBLE_APP_BASE_URL=https://stats.example.com FEASIBLE_APP_LISTEN=127.0.0.1:19301 FEASIBLE_APP_DATA_DIR=./data FEASIBLE_INGEST_SALT=$(openssl rand -hex 32) FEASIBLE_INGEST_TRUSTED_PROXIES=127.0.0.1,::1 FEASIBLE_OPERATOR_EMAIL=you@example.com EOF
FEASIBLE_INGEST_TRUSTED_PROXIES is for the TLS proxy you'll run on the same machine (see below). Leave it out and every visitor arrives as 127.0.0.1, so locations come out unknown, people on the same browser count as one visitor, and the bot filters judge your proxy instead of the visitor.
Then create the databases, make your account and start it:
set -a; . ./feasible.env; set +a
./feasible db migrate ./feasible account create --email you@example.com --name "Your Name" ./feasible serve
account create prints a generated password once. Sign in at your base URL, add a site, and paste the snippet it shows you into your pages' . The heart of it is one tag:
<script defer data-domain="example.com" src="https://stats.example.com/js/script.js"></script>
A few things worth knowing:
- TLS.
servespeaks plain HTTP. Put any TLS proxy in front of it, Caddy or nginx, and setFEASIBLE_APP_BASE_URLto the publichttps://address. With Caddy on the same machine, this is the whole config:
stats.example.com {
reverse_proxy 127.0.0.1:19301 { header_up -X-Feasible-IP header_up -CF-Connecting-IP } }
Caddy sets X-Forwarded-For itself. The two header_up lines drop headers Feasible would believe ahead of it, so a visitor can't send their own. With nginx, set proxy_set_header X-Forwarded-For $remote_addr; and set those two headers to "".
- Trusted proxies.
FEASIBLE_INGEST_TRUSTED_PROXIEStakes addresses or CIDR ranges, comma-separated, and bothserveandingestread it. Only connections from that list may say who the visitor is. It's empty by default, which is right only when nothing sits in front of Feasible. Behind a load balancer or CDN, add its ranges too. Leave it out behind a proxy and ten wrong passwords from anyone lock everyone out of sign-in for 15 minutes. - `FEASIBLE_APP_HOSTED=false` turns off billing, trials, usage limits and public sign-up. Every feature stays on. Run
account createagain for each separate account; teammates join by invitation from inside the app. - Email. The default
logtransport writes messages totmp/mail/and sends nothing. SetFEASIBLE_APP_MAIL_TRANSPORT=smtpandFEASIBLE_SMTP_HOSTso password resets and reports actually arrive. - Locations. Drop the free DB-IP Lite country or city
.mmdbfile intodata/geoip/. Without one, locations show as unknown and everything else works. - Google. Sign-in with Google, the GA4 import and Search Console terms share one OAuth client:
FEASIBLE_GOOGLE_CLIENT_IDandFEASIBLE_GOOGLE_CLIENT_SECRET. Leave them unset and those features hide themselves. - Backups.
./feasible db backupwrites a consistent snapshot of every database. Don'tcpfiles a running process is writing.
Every variable is documented in .env.sample. The full guide is at feasible.lol/docs/self-hosting.
What's in it
- One-page dashboard. Visitors, visits, pageviews, bounce rate, visit duration, channels, sources and all five UTM tags, pages with entry and exit, countries, regions and cities, devices, browsers, operating systems and languages. Realtime, filters and period comparison.
- Goals and funnels. Custom events and properties, funnels of 2 to 8 steps, revenue by source, scroll depth, outbound links, file downloads and 404s. Core Web Vitals, if you turn them on.
- Search terms people used to find you, from Google Search Console.
- Imports. Google Analytics 4 history by connecting your Google account, or CSV exports from another tool. Export your raw data any time.
- Reports and alerts. Weekly and monthly email and Slack reports, traffic spike and drop alerts, annotations.
- Sharing. Teams with roles, guest access to a single site, public or password-protected dashboards, two-factor login.
- Bot filtering you can inspect. Every dropped event is counted with the reason it was dropped.
- API. One key type for the Stats API, the Sites API and signed webhooks.
- MCP. Connect Claude, ChatGPT, Cursor or VS Code by pasting one URL and approving it, then ask "why did traffic drop last week?" in plain words.
feasible mcpserves the same tools over stdio. - Integrations in
ecosystem/: a WordPress plugin, a Google Tag Manager template, a Looker Studio connector, an npm package for the tracker, and SDKs for Go, Node, PHP, Python and Ruby. They aren't published to their stores yet, so install them from here.
How it's built
- Go, one binary. The React dashboard, the server-rendered pages, the tracker, email templates, migrations and the bot lists are all embedded with
go:embed. The release archive is about 8 MB. Nothing to copy alongside it. - SQLite, one database per account. A small
system.dbholds users, teams and sites. Each account's events live in their own file, through a pure Go driver, so there's no cgo. One directory is the whole install. - Ingest. The tracker posts to
/api/event. The IP address is used in memory for geolocation and a daily-salted visitor hash, then dropped before anything is written. Self-hosted, events are batched and committed straight to the account's database. Hosted, separate ingest processes commit each event to a local SQLite outbox, answer202, and forward signed batches to the app server that owns the site. A row leaves the outbox only after that server confirms the commit. - Reports read hourly and daily roll-up tables, so a year of data answers in under a second.
- The tracker is plain JavaScript, about 3.6 KB gzipped. The build fails if it grows past 3.75 KiB. Web Vitals is a separate module that loads only on sites that turn it on.
- Disk. A million pageviews takes about 300 MB once indexed and rolled up. Write and read numbers, and how they were measured, are in
internal/bench/RESULTS.md.
Why
Privacy-friendly analytics is usually priced per site, per seat or per pageview tier, with funnels, revenue and the API saved for the top plan. Self-hosting it usually means Docker, a separate analytics database and a few gigabytes of RAM before you count a single visit.
Feasible is one price with everything in it. The self-hosted build is the same build, with nothing taken out. If you can run a binary, you can run it.
Developing
You need Go 1.26 or newer. Node is needed to rebuild the dashboard, the stylesheet or the tracker. Caddy is only needed for the three-process mode.
cp .env.sample .env
make build # compile the front end, then the binary make dev-solo # one process, everything in it: the self-hosted shape
For the hosted shape, run each process in its own terminal so its logs stay readable:
make caddy # :19300, the only port you open in a browser
make app # :19301, the app and signed internal routes make ingest # :19302, events and health make testsite # :19303, a real page with the snippet installed
make dev runs all three at once. Every runnable target has a -ts twin (make app-ts, make dev-ts) that binds to the Tailscale address and moves FEASIBLE_APP_BASE_URL with it, so the app is reachable from another machine. make on its own lists everything.
You don't need local services to develop. Email is written to tmp/mail/, a missing geolocation file means "unknown", and Stripe webhooks come through the CLI:
stripe listen --forward-to localhost:19301/webhooks/stripe
FEASIBLE_APP_TRANSPORT picks who owns /api/event: direct writes from the app process, and http hands it to separate feasible ingest processes. .env.sample covers the shard and signing settings for the split topology, and ops/load-balancer.md covers failure and drain behavior. Before the hosted service takes traffic, feasible billing preflight --checkout-smoke checks its Stripe setup.
Health
Every process serves three endpoints on its one listener:
curl https://app.feasible.lol/health # public: can customers use the site
curl localhost:19301/health/live # internal: is this process running curl localhost:19301/health/ready # internal: may this process take traffic
Point an uptime monitor at the public /health and check the status code. /health/live checks nothing on purpose, so a slow database can't turn into a restart loop. /health/ready returns 503 with a JSON body naming every failed dependency. There's no /metrics endpoint.
ops/ holds the runbooks, the load balancer settings and the game day that breaks things on purpose to prove the runbooks right.
Before you push
make test
make lint make check-env # every environment variable is documented in .env.sample
Cutting a release
Releases are a deliberate choice, never automatic. When main is stable, run the Release workflow from the Actions tab. Leave the version blank to bump the patch number, or give one like 1.2.3. It tags main, creates the GitHub Release and attaches Linux, Windows and macOS builds for amd64 and arm64 with a SHA-256 checksum file.
License
GNU AGPL-3.0-or-later. Run it, change it and self-host it freely. If you offer it to others as a network service, you have to make your source available to those users.
[feasible.lol](https: