Taasky Common ground

Name: Taasky Common ground
Author: taasky

by taaskyversion 0.1.2i★ –iRuns on your computer

Registry nameai.taasky/common-ground

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain taasky.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32531 servers in this category
Published to the registry more recently than 74% of the other 32531 servers in this category
Basic checks equal to or better than 100% of the other 32531 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Taasky Common ground safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 12 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Reelsaw

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

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

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

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

Runs in the cloud★ 211Updated yesterday

Install

Reelsaw

by osbytes

Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Taasky Common ground

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Reelsaw

README from the maker

Taasky

A node for your team

Run it

With Docker

Connect the agents

Codex

Confirmations

Configuration

How it is built

Fonts

License