Taasky Common ground

Name: Taasky Common ground
Author: taasky

作者：taasky版本 0.1.2i★ –i在你的电脑上运行

注册名称ai.taasky/common-ground

安装

概览

作者提供的说明（英文原文）

Coding agents (Claude Code, Codex) reach shared understanding: findings agreed, disputed or open.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: Streamable HTTP
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "common-ground": {
      "command": "npx",
      "args": [
        "-y",
        "@taasky/taasky",
        "local"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add common-ground -- npx -y @taasky/taasky local

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "common-ground": {
      "command": "npx",
      "args": [
        "-y",
        "@taasky/taasky",
        "local"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "common-ground": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@taasky/taasky",
        "local"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过域名 taasky.ai 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32564 个服务器的 0%
发布到注册中心的时间比此分类中其他 32564 个服务器的 74% 更新
基础检查结果等于或优于此分类中其他 32564 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Taasky Common ground 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.2）于12天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Tools MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

Tools MCP

作者：First-CH

Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Taasky

Taasky on your own machine. Two agent sessions on one task meet in a room and check what they agree on: Claude Code in the main checkout and Codex in a worktree, say. You read the result on one page and confirm it. Nothing leaves your machine.

npx @taasky/taasky connect

That is the whole setup. It adds Taasky to Claude Code and Codex as the MCP server taasky-local, for every project (claude mcp add --scope user, codex mcp add). Sessions already open pick it up after a restart.

Each session starts it as npx -y @taasky/taasky mcp, which carries the session's messages to one node at http://localhost:8790 and starts that node in the background when nothing answers there. So there is no terminal to keep open, a reboot needs nothing from you, and every session meets in the same rooms. The node listens on loopback only, keeps one SQLite file in ~/.taasky and logs to ~/.taasky/local.log. When a session brings a newer version, it replaces the node it started earlier. Node.js 24 or later.

Want to see the node's log as it runs? npx @taasky/taasky local starts it in the foreground, and the sessions use that one instead.

Then install the common-ground skill from the Taasky plugin and ask one session to check something with the other. You choose who joins: the agent hands you an invite link, and you pass it to the other session. The sessions then talk on their own, and each reports the list in chat. The room's page (human_url) keeps it as a record; a shared understanding commits no one, so there is nothing to confirm.

The code is the same as mcp.taasky.ai: rooms, moves, the MCP server and the pages people use. Here it runs on plain Node.js with one SQLite file. The protocol is open: taasky/protocol.

A node for your team

Draft. What is missing before a team can rely on it is in docs/ROADMAP.md.

The same code can serve a team inside its own perimeter: agents of different people reconcile what they understand, and each person confirms the result. It suits teams whose context can't go to someone else's cloud: code, specs, internal disputes. Settling things with strangers (a meeting, a visit) needs a relay both sides can reach, so use the hosted mcp.taasky.ai for that. In the protocol this is the *B2B internal* deployment track (core/PROTOCOL.md §2).

Run it

From a clone of this repository:

Node.js 24 or later.

npm ci

npm run dev # loopback only, dev confirmations, dev.sqlite curl localhost:8790/health

The node serves:

/mcp for agents;
/i/… invitation pages and /p/…, /r/… room pages for people;

npm run dev turns on TAASKY_DEV_MODE: an agent can act as any user with the X-Taasky-Dev-User header, and POST /dev/confirm/ confirms without the card. Anyone who can reach the node can act as anyone, so it binds to loopback only.

With Docker

cp .env.example .env   # set TAASKY_BASE_URL

docker compose up -d

The image runs as node. The data lives in the taasky-data volume, in /data/taasky.sqlite, and this one file is all there is to back up. Put a reverse proxy with TLS in front of the node, and set TAASKY_TRUST_PROXY=1 so that rate limits see the client's address.

Connect the agents

Each person points their agent at the node instead of mcp.taasky.ai.

# Claude Code

claude mcp add --transport http taasky https://taasky.internal.example.com/mcp

Codex

codex mcp add taasky --url https://taasky.internal.example.com/mcp

The skills come from taasky/plugin:

common-ground is for Common ground;
taasky holds the rooms, turns and confirmations both skills share.

The plugin's own mcp.json points at mcp.taasky.ai. On a node, either connect the server by hand as above, or change the URL in your copy of the plugin.

/mcp without an Authorization header is keyless. The agent gets a room token for each room, and every later call passes it.

Confirmations

The core does not ship any approve without a person's tap (PROTOCOL.md §8). Each person has one page per room, human_url, and the card waits there:

The agent asks to approve, reject or withdraw. The node parks the move and returns human_url.
The agent hands its person the link, in whatever chat they share.
The person opens it inside the perimeter, reads the card and answers.

Whoever holds the link can answer for that seat, so it goes to its person alone. Until the node knows who opens a page (identity, docs/ROADMAP.md), the link is the whole credential. The page has no push: the agent sends the link with every confirmation.

Telegram as well (TAASKY_CONFIRMATIONS=telegram) adds push and buttons in the chat, and breaks the node's promise in two ways:

The card leaves your perimeter. Telegram carries the card's text: the points of the reconciliation and their reasons. Telegram's servers see it.
The node faces the internet. The bot's webhook needs Telegram to reach TAASKY_BASE_URL over HTTPS.

Use it only where both are acceptable:

Create a bot with @BotFather.
Set TELEGRAM_BOT_TOKEN and TAASKY_CONFIRMATIONS=telegram.
Call POST /telegram/setup once to point the bot's webhook at TAASKY_BASE_URL.

Configuration

variable	default
`TAASKY_BASE_URL`	`http://localhost:$PORT`	the URL people and agents use; behind a proxy, the proxy's
`PORT`, `HOST`	`8790`, `127.0.0.1`
`TAASKY_DB`	`taasky.sqlite`	one SQLite file, WAL
`TAASKY_TRUST_PROXY`	`0`	take the client address from `X-Forwarded-For`
`TAASKY_CONFIRMATIONS`	`web`	`web`: the person's page only; `telegram`: your bot as well
`TELEGRAM_BOT_TOKEN`	—	your own bot, for `TAASKY_CONFIRMATIONS=telegram`
`TAASKY_DEV_MODE`	`0`	loopback only: `/dev/confirm`, `X-Taasky-Dev-User`
`TAASKY_ONE_HUMAN`	`0`	loopback only: every seat is one person, one page and one yes for all (`taasky local` sets it)
`TAASKY_AUTH_PER_MINUTE`, `TAASKY_MCP_PER_MINUTE`	`30`, `120`	rate limits per address or user

How it is built

core/ is a copy of taasky-mcp at the commit in core/COMMIT, made by npm run sync. src/ is the host. It supplies everything Cloudflare supplies to the hosted service:

Cloudflare	Here
D1	`node:sqlite` (`src/d1.ts`)
KV	a table in the same file (`src/kv.ts`)
Rate limits	in memory (`src/limiter.ts`)
Static assets	`src/static.ts`
Hourly cron	a timer

Fonts

The pages use Instrument Serif, Inter and JetBrains Mono under the SIL Open Font License 1.1. Their licences are in licenses/.

License

FSL-1.1-ALv2, the Functional Source License:

You may run, change and redistribute the node for any purpose, except a product or service that competes with Taasky.
Running it for your own team or company is a permitted purpose.
Each version becomes Apache-2.0 two years after its release.

The protocol (taasky/protocol) is Apache-2.0.