Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Runs in the cloud
no_human
Overview
Description from the maker (original English)
File a task with your local no_human and check on it: task_add and task_status over stdio.
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
- UsageiVery new↓ 44/wk · ★ –
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: stdio
- Category: Docs, sheets & office work
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
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
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": {
"no-human": {
"command": "uvx",
"args": [
"no-human",
"mcp-serve"
]
}
}
}Run this in your terminal
claude mcp add no-human -- uvx no-human mcp-serveOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"no-human": {
"command": "uvx",
"args": [
"no-human",
"mcp-serve"
]
}
}
}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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"no-human": {
"type": "stdio",
"command": "uvx",
"args": [
"no-human",
"mcp-serve"
]
}
}
}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 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account no-human-ai, which owns the repo
- … 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 Docs, sheets & office worki
- More stars than 0% of the other 3576 servers in this category
- Published to the registry more recently than 37% of the other 3576 servers in this category
- Basic checks equal to or better than 100% of the other 3576 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 no_human 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.2.3) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Excel MCP Server
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Runs on your computer
MCP Server for Excel
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Runs on your computer
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.
no_human
From ticket to reviewed pull request. *Free and open-source, on your machine.*
English · 简体中文 · 日本語 · 한국어 · Español · Français · Deutsch · Português (Brasil)
getnohuman.com · Quickstart · Docs · Watch it work a sprint · Discord
▶ Watch the loop — a ticket in, a reviewed pull request out; the whole loop in 57 seconds.
The AI coding factory you can trust :
- A plan before any code, from the ticket plus what it finds in your repo. When planning fails, the coder is told it is working without one; when the change is judged trivial the plan is skipped without telling the coder, by design — the skip is still stated in the run's event stream.
- An adversarial review. A different model, in a session that never saw the coder's transcript, told to refute "done". You get a pass/fail checklist citing file and line — never a numeric self-score.
- A tamper guard. Deleted tests, new skips, an assertion turned into a tautology — counted mechanically before the review gate runs, then justified against your acceptance criteria or the attempt stops.
- Proof the fix fixed the bug. The tests offered as evidence must fail at the merge base and pass on the new tree — the reproduction gate runs both. Out of the box that binds a Python bug fix;
repro_gate.mode: requiredbinds every kind and every change. - Your tests run, locally and optionally through your CI — and a PR that found no test command says NOT RUN on its face.
- An honest stop. When it cannot finish it stops and says why — a specific question when your answer would unblock it, a structured record when it has simply run out of budget — never an invented plausible diff.
What the gate caught
no_human builds no_human. Over 65 days on its own board, none of this reached a pull request:
- 505 of 1,709 attempts the coder called done were sent back by the second model, each with a pass/fail checklist citing file and line.
- 44 attempts were stopped before the review even ran, for deleting or weakening a test.
- 46 bug-fix proofs were refused because the test offered as evidence passed on the old code too.
Install
One line (CLI + board)
uv tool install no-human # or: pipx install no-human — the wheel ships the boardnh init && nh doctor # token, config, first repo; then prove the install is real
Desktop app
Each release ships a SHA-256 alongside the artifact. Platform notes and the first-run walk-through: docs/quickstart.md.
From source
git clone https://github.com/no-human-ai/no_human.git && cd no_humanuv sync # installs the nh entry point into .venv (cd web && npm install && npm run build) # builds the board (cold first install can take minutes) uv run nh init # token, config, first repo (about 2 minutes) uv run nh doctor # verify the install is real before relying on it
The web build is not optional if you want the board: a source checkout ships no web/dist, so without it nh start serves the API only and renders no UI. Needs Python 3.12+, uv, git, and Node with npm for the board build.
Product highlights
A plan before any code Acceptance criteria you can check, written from the ticket and your repo.
An independent reviewer A second model that never saw the coder's session, told to refute "done". Pass or fail; every finding that blocks cites file and line.
Your tests, on the PR's face Run locally or through your CI. No test command found reads NOT RUN , never blank.
A tamper guard Deleted tests, new skips and tautological assertions are counted before review. Unjustified, the attempt stops.
Proof the fix fixed the bug The tests offered as evidence must fail on the old code and pass on the new. The gate runs both, and the event log shows the verdict.
An honest stop When it needs you, it parks with one specific question instead of guessing.
Your tracker's tickets, on your board Pick Jira or Linear tickets from the backlog (monday.com boards are polled). Each one is scoped with you before it starts.
Stills: the real board on a demo workload.
Run one task
Run nh with no arguments for the shell: your lanes, a live event tail, and an intake you describe a task to in plain English. Every command below still works.
nh # the shellnh start # board + worker on 127.0.0.1:8420 nh task add https://github.com/org/repo/issues/42 --repo ~/git/repo nh status # needs-you / working / waiting / done nh review # the reviewer's evidence checklist nh diff # the diff it wants to ship nh approve # your approval squash-lands the PR (git.approve_identity) nh reject --reason "..." # send it back with feedback
Integrations
Point no_human at the tracker you already use and it pulls the tickets to your board — a tracker's filter lives in your config, never in a task's own text, and a transport error logs and retries on the next tick instead of crashing the pool.
| Tracker | How tickets arrive | Filter you configure |
|---|---|---|
| Jira Cloud | Polled via REST search/jql (HTTP Basic email:token) | integrations.jira.jql |
| Linear | Polled via the GraphQL API | integrations.linear.team_key + state_types + label |
| monday.com | Polled via GraphQL v2 | integrations.monday.board_id + status_column + todo_labels |
With write-back on (write_back, off by default), the ticket moves with the task — matched by status category, type, or the label you name, never a hard-coded transition id — and gets the PR link; a task that needs a human is commented on, never transitioned. GitHub and GitLab issues import as tasks by URL, and PRs or MRs open on your own host; Slack and Teams get a message when a task needs you; Jenkins and CircleCI can run your test layers and gate the loop. Setup for each: docs/adapters.md.
Watch the Jira flow end to end — tickets synced from a Jira board, scoped, implemented, and delivered as a review-passed pull request (click for the full video with every step):
▶️ Play the full demo — 1:33, from Jira board to review-passed PR
GitHub Action
Run the same adversarial reviewer and tamper guard as a pull-request check — one shot, no daemon, no ~/.no_human database, and not the queueing nh review CLI path. It judges the diff alone: unlike a local run, it collects no lint, wiring or type evidence and does not explore the repository. It posts a single pass/fail checklist comment with file:line citations, found by its own marker and updated in place on every run rather than creating a new one e
Only the beginning is shown; read the rest in the repo