timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Favro cards, boards and collections over MCP: read, search, write, and resolve names to ids.
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 Favro 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Favro,或回答中出现 Favro 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Favro
Favro 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
Claude Code 暂时无法连接 Favro
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Favro 的应用
Cursor 暂时无法连接 Favro
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Favro 的应用
VS Code 暂时无法连接 Favro
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Favro 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 mmedum 验证,该账户拥有此仓库
代码最后更新于3天前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/mmedum-favro-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于3天前,最新版本(4.4.2)于13天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 Favro | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | Apache-2.0 | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Favro as MCP tools. Find, read and change cards, boards and collections from Claude or any MCP client.
A single Go binary that speaks Model Context Protocol over stdio. It runs as a subprocess of your client, on your own machine, against one Favro organization, with your own address and API token. There is no server to host and no shared deployment.
It is for a person who works in Favro and wants an assistant to do that work with them: find a card by what it says, read it with every id turned into a name, move it, edit its description in place, tag it and comment on it. Beyond Favro's REST API, it resolves names to ids, searches card text and reads a whole card in one tool call, so a model spends its calls on the work rather than on lookups.
Unofficial. Not affiliated with or endorsed by Favro.
Goals:
confirm: true. The ordinary writes share only inside the organization, the upload tools read one directory, and a mistyped tag name never becomes a tag.Non-goals:
Each tagged release publishes a favro-mcp_ .mcpb on the GitHub Releases page. Opening it installs the server into Claude Desktop and prompts for what it needs: your Favro address, an API token and the organization id. There is no config file to edit by hand.
It also asks for the settings a config file would carry. The destructive tools (enable_destructive) stay off unless you turn them on, and so do uploads until you pick an upload folder (upload_dir). This server asks nobody before a call. Claude Desktop approves each tool, and a tool you always allow then runs unasked, so leave enable_destructive off unless you need its tools.
The bundle carries a macOS universal binary, a Windows amd64 binary, and both Linux architectures behind a launcher that picks at startup. It is listed in checksums.txt and covered by the release signature; see Verifying a download.
Each stable (non-pre-release) release publishes a single multi-arch favro-mcp.plugin zip on the GitHub Releases page. The bundle contains binaries for darwin-amd64, darwin-arm64, linux-amd64, linux-arm64 and windows-amd64. On macOS and Linux a launcher shim picks the right one at runtime, and on Windows a .cmd shim runs the windows-amd64 binary, which Windows on arm64 (windows-arm64) runs under emulation.
favro-mcp.plugin from the release.favro MCP server appears with its tools registered.The bundled .mcp.json points at ${CLAUDE_PLUGIN_ROOT}/bin/favro-mcp so the install is relocatable; no host paths to edit.
For non-Cowork hosts (Claude Code via raw .mcp.json, MCP Inspector, custom integrations):
favro-mcp_ _ _ .tar.gz (or .zip on Windows) from the release.favro-mcp binary somewhere on $PATH (or note its absolute path).go install github.com/mmedum/favro-mcp/v4/cmd/favro-mcp@latest
Or build a clone:
git clone https://github.com/mmedum/favro-mcp
cd favro-mcp make build # → bin/favro-mcp
Either needs the Go version go.mod declares. Under the default GOTOOLCHAIN=auto an older toolchain downloads it on demand; under GOTOOLCHAIN=local the build fails instead of downgrading.
Every release carries checksums.txt, an SBOM per archive, a keyless cosign signature over the checksum file, and build provenance attested by GitHub. Both bundles, favro-mcp.plugin and the .mcpb, are in checksums.txt with the archives, so one signature covers all of it.
# 1. The file is what the release says it is.
sha256sum -c checksums.txt --ignore-missing
cosign verify-blob checksums.txt \ --bundle checksums.txt.bundle \ --certificate-identity-regexp '^https://github\.com/mmedum/favro-mcp/' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com
gh attestation verify favro-mcp_ _ _ .tar.gz --repo mmedum/favro-mcp gh attestation verify favro-mcp.plugin --repo mmedum/favro-mcp
Builds are reproducible: -trimpath plus the commit's own timestamp, so rebuilding a tag gives byte-identical archives.
The server uses Favro's HTTP Basic Auth (user email + API token), scoped to one Favro organization at startup. Tools never accept organization_id — pass it once via env var or keyring and forget about it.
API tokens are user-scoped — for team installs, generate the token from a dedicated service-style Favro user with the minimum permissions you need, not from a personal account.
Two sources, checked in order; the first one that produces a complete (email, token, organization_id) triple wins:
FAVRO_USER_EMAIL, FAVRO_API_TOKEN, FAVRO_ORGANIZATION_ID.favro-mcp auth login (cross-platform: macOS Keychain, Windows Credential Manager, Linux Secret Service).These variables change how the server runs rather than who it runs as:
| Variable | Effect |
|---|---|
FAVRO_LOG_LEVEL | debug / info (default) / warn / error. Logs go to stderr; stdout carries only the MCP protocol stream. |
FAVRO_MCP_SKIP_VALIDATE | Set to true to skip the startup call that checks the credentials against Favro. For offline testing; the server then fails on the first real tool call instead of at startup. false, 0 and anything it cannot read as true leave the check on. |
FAVRO_ENABLE_DESTRUCTIVE | Set to true to register the destructive tools: the deletes, favro_remove_attachment, favro_replace_dependencies and favro_widen_collection_sharing. Off by default, and "off" means they are absent from tools/list rather than guarded — a host in an auto-approve mode runs a tool without prompting, so not registering it is the only guarantee. Anything the value cannot be read as true leaves them off. Each call must also pass confirm: true. |
FAVRO_UPLOAD_DIR | The one directory the upload tools read files from, as an absolute path. Unset, and they are not registered. Nothing outside it is read, and a link out of it is refused. |
Every variable, the credentials included, is read without the spaces around its value, and spaces alone count as unset.
FAVRO_REQUIRE_PROMPT and FAVRO_INTERACTION_HINT are removed; unset them. docs/configuration.md has every setting.
Your MCP client approves each call; the server does not ask you itself. claude.ai and Codex ask before any write that changes or removes something, which says destructiveHint: true. A write that only adds, such as a new card, comment or attachment, says false. VS Code asks before every tool that writes.
In Claude Code, these tools ask on every call whatever your rules say: favro_delete_tag, favro_delete_group, favro_delete_widget and favro_delete_collection, whose loss reaches past the one thing deleted, and favro_widen_collection_sharing, which opens a collection to the whole organization or to anyone with its link. Where no prompt can be shown, as in claude -p, Claude Code refuses them. For the rest, list the calls you want to approve one by one under permissions.ask in your settings, with the name you gave the server in place of favro. For example, the writes that share, publish, send a file or delete:
{
"permissions": { "ask": [ "mcpfavrofavro_create_collection", "mcpfavrofavro_update_collection", "mcpfavrofavro_widen_collection_sharing", "mcpfavrofavro_create_group", "mcpfavrofavro_update_group", "mcpfavrofavro_upload_attachment", "mcpfavrofavro_upload_comment_attachment", "mcpfavrofavro_delete_tag", "mcpfavrofavro_delete_group", "mcpfavrofavro_delete_widget", "mcpfavrofavro_delete_collection", "mcpfavrofavro_delete_column", "mcpfavrofavro_delete_card", "mcpfavrofavro_delete_comment", "mcpfavrofavro_delete_task", "mcpfavrofavro_delete_tasklist", "mcpfavrofavro_delete_webhook", "mcpfavrofavro_remove_attachment", "mcpfavrofavro_replace_dependencies", "mcpfavrofavro_delete_dependency", "mcpfavrofavro_delete_all_dependencies" ] } }
What holds whatever the client does:
FAVRO_ENABLE_DESTRUCTIVE=true, and each call must pass confirm: true; dry_run: true previews without it.favro_widen_collection_sharing opens a collection, and takes the collection's name as well as its id, so the prompt shows which one.favro_delete_widget takes collection_id or everywhere: true, and refuses a call with neither.auth subcommandsfavro-mcp auth login # interactive: masked token input, writes to keyring
favro-mcp auth status # show user/org (token never printed) favro-mcp auth logout # delete keyring entries favro-mcp auth which # print active credential source: env or keyring favro-mcp doctor # check credentials, org bi