Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Know what's gaining traction online: breakout topics in tech, sports & politics, with citations.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.upriver.ai/mcp在终端中运行这条命令
claude mcp add --transport http upriver https://mcp.upriver.ai/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"upriver": {
"url": "https://mcp.upriver.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"upriver": {
"type": "http",
"url": "https://mcp.upriver.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.upriver.ai/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 upriver.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.0)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AI Deprecations
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Upriver MCP
Real-time context on creators, audiences, brands, trends, and sponsorships — for AI applications.
Upriver provides an API that turns what's happening online into real-time, reliable context for AI applications. It delivers evidence-backed signals — each grounded in real sources — across:
This repository is the home of Upriver's Model Context Protocol (MCP) server, which brings that context to any MCP-compatible AI assistant or agent.
| Endpoint | https://mcp.upriver.ai/mcp |
| Transport | Streamable HTTP |
| Auth | Sign in with Upriver (OAuth), or send your Upriver API key in the X-API-Key header |
It's a remote, hosted server — nothing to install or run. OAuth sign-in works in every client. The X-API-Key header is supported by Claude Code, Cursor, VS Code, Cline, Windsurf, Codex CLI, Goose, and Zed — but not by Claude's or ChatGPT's connector UIs, which are OAuth-only.
claude mcp add --transport http upriver https://mcp.upriver.ai/mcp
To use an API key instead of OAuth, pass it as a header:
claude mcp add --transport http upriver https://mcp.upriver.ai/mcp \
--header "X-API-Key: YOUR_UPRIVER_API_KEY"
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project), then connect it in Settings → Tools & Integrations to sign in:
{ "mcpServers": { "upriver": { "url": "https://mcp.upriver.ai/mcp" } } }
For API-key auth, add "headers": { "X-API-Key": "YOUR_UPRIVER_API_KEY" }.
VS Code uses a different shape — top-level `servers` and a required `"type": "http"`. Add to .vscode/mcp.json (or run MCP: Add Server):
{ "servers": { "upriver": { "type": "http", "url": "https://mcp.upriver.ai/mcp" } } }
For API-key auth, add "headers": { "X-API-Key": "YOUR_UPRIVER_API_KEY" }.
In Claude, go to Customize → Connectors → "+" → Add custom connector, name it Upriver, paste https://mcp.upriver.ai/mcp, then Connect and sign in. (Claude's connector is OAuth-only — there's no field for an API key, and don't add a raw url entry to claude_desktop_config.json; the desktop app rejects it.)
Use the Remote Servers tab (Transport: Streamable HTTP), or edit cline_mcp_settings.json — the type field is required, or Cline falls back to legacy SSE and fails:
{ "mcpServers": { "upriver": { "type": "streamableHttp", "url": "https://mcp.upriver.ai/mcp" } } }
Edit ~/.codeium/windsurf/mcp_config.json — Windsurf's field is `serverUrl`:
{ "mcpServers": { "upriver": { "serverUrl": "https://mcp.upriver.ai/mcp" } } }
More clients — Codex CLI, ChatGPT, Goose, Zed
Codex CLI (OpenAI)
codex mcp add upriver --url https://mcp.upriver.ai/mcp --header X-API-Key=YOUR_UPRIVER_API_KEY
ChatGPT — Enable Developer mode (Settings → Apps & Connectors → Advanced), then Settings → Connectors → Create, name it Upriver, paste https://mcp.upriver.ai/mcp, choose OAuth, and sign in. (No custom-header field — OAuth only in the UI.)
Goose — add to ~/.config/goose/config.yaml:
extensions:
upriver: type: streamable_http uri: https://mcp.upriver.ai/mcp enabled: true headers: X-API-Key: "${UPRIVER_API_KEY}"
Zed — add to settings.json under context_servers:
{ "context_servers": { "upriver": { "url": "https://mcp.upriver.ai/mcp", "headers": { "X-API-Key": "YOUR_UPRIVER_API_KEY" } } } }
Most clients use the Cursor shape above (mcpServers + url, optional headers). For agents that read install manifests, see llms-install.md.
JetBrains IDEs: MCP works, but the IDE currently drops custom request headers and
doesn't yet support OAuth for remote servers, so Upriver's
X-API-Keyauth can't
connect there yet — we'll list it once JetBrains ships the fix.
The MCP server currently exposes Upriver's breakout topics — emerging subjects gaining traction online across tech, sports, and politics, each returned with grounded source citations so the model reasons from real evidence instead of guessing.
Both tools are read-only. Each returns up to limit topics (default 10, max 25), every topic carrying up to 5 source citations, plus a has_more flag when more topics exist beyond the page.
breakout_search_topicsSearch breakout topics by keyword.
| Parameter | Type | Description |
|---|---|---|
query | string · required | Natural-language search, e.g. "AI video effects". |
vertical | enum | Restrict to tech, sports, or politics. |
limit | integer | 1–25 (default 10). |
citation_sources | array | Restrict citations to any of news, reddit, twitter. |
breakout_list_topicsBrowse breakout topics gaining traction right now.
| Parameter | Type | Description |
|---|---|---|
vertical | enum | Restrict to tech, sports, or politics. |
status | enum | Lifecycle filter: active (default), emerging, trending, declining, detected, or all. |
limit | integer | 1–25 (default 10). |
citation_sources | array | Restrict citations to any of news, reddit, twitter. |
Each topic includes its name, vertical, lifecycle status, a momentum signal, and its top citations (title, URL, source category, and publish time).
Breakout topics are the first slice of the Upriver API to land as MCP tools. The full API — Creators, Audiences, Brands, Products, Trends, and Sponsorships — is documented at [docs.upriver.ai](https://docs.upriver.ai), and we're rolling those endpoints out as MCP tools. Watch this repository for new tools as they ship.
Upriver MCP access is provisioned per account. Request access at dashboard.upriver.ai or email support@upriver.ai. Once your account is enabled, the same Upriver sign-in (or API key) works across every MCP client.
The contents of this repository — connection documentation and listing metadata — are released under the MIT License.
The hosted Upriver MCP service and the Upriver API are operated by Potato Laboratories, Inc. d/b/a Upriver and are governed by Upriver's Terms of Service. The MIT License covers this repository only — not the service, nor the data it returns. "Upriver" and the Upriver logo are trademarks of Potato Laboratories, Inc. and are not covered by the MIT License.