Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Stable eight-tool MCP server for changed-UI assurance, authority-aware UI task context, and repair.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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": {
"decantr-ai": {
"command": "npx",
"args": [
"-y",
"@decantr/mcp-server"
]
}
}
}Run this in your terminal
claude mcp add decantr-ai -- npx -y @decantr/mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"decantr-ai": {
"command": "npx",
"args": [
"-y",
"@decantr/mcp-server"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"decantr-ai": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@decantr/mcp-server"
]
}
}
}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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
The registry name was verified with the GitHub account decantr-ai, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (3.11.5) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
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
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
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.
Help AI build like it belongs here.
Agent-neutral UI change control for codebases edited by AI.
Website · Get started · Documentation · Discord
Decantr checks the UI change an AI coding agent actually made against the components, styles, interaction rules, and source boundaries already owned by your project. It reports a small set of source-anchored findings without replacing your stack or generating the change itself.
No account, setup, or adoption step is required:
npx @decantr/cli@3.11.4 verify
CHANGED UI PROJECT AUTHORITY VERIFY RESULT
What the agent → What your app → Compare the → Pass, attention, actually edited already owns current change or not proven
Bare verify is read-only. It resolves the current Git change, selects exactly one changed UI app only when that choice is provable, and returns at most three consequential findings with source and repair targets.
| Built for adoption | What that means |
|---|---|
| Works before setup | Run it against the current change in an existing Git worktree. |
| Respects project authority | Production source, components, styling, tests, and accepted local rules remain in control. |
| Agent-neutral | Use the CLI, JSON, CI, or MCP with the coding agent and editor you already use. |
| Fails closed | Ambiguous apps, missing Git scope, and unsupported authority return not_proven, not a reassuring score. |
Changed-UI Assurance is the zero-setup entry point. Teams can deepen it into an authority-aware workflow when they need durable task context and CI evidence.
npx @decantr/cli@3.11.4 scan
npx @decantr/cli adopt --yes # one-time attachment npx @decantr/cli task /feed "add saved actions" npx @decantr/cli verify --full npx @decantr/cli ci init # one-time CI setup
In a monorepo, install once at the workspace root and select the app consistently:
pnpm add -D -w @decantr/cli
pnpm exec decantr scan --project apps/web pnpm exec decantr adopt --project apps/web --yes pnpm exec decantr task /feed "add saved actions" --project apps/web pnpm exec decantr verify --project apps/web
scan and bare verify are read-only. adopt is the explicit one-time write boundary. Use verify --full for Project Health and its evidence or baseline options.
Routes are evidence, not the product ontology. Decantr can reason about routes, layouts, reusable components, stories, overlays, flows, design-system packages, runtime states, and exact source files.
It evaluates authority on independent axes:
The deeper workflow reports ready, limited, blocked, or unsupported. A numeric score never hides an unresolved axis. Source declaration and deployment reachability remain separate facts, and tests, fixtures, stories, generated files, build output, and sibling apps never become production authority.
See UI authority and workflow for the complete model.
Decantr does not replace your router, component library, styling system, tests, design tools, editor, or coding agent.
CLI and verifier 3.11.4, with MCP server 3.11.5, correct component-reuse import advice while preserving the existing report schemas and eight-tool MCP surface. A feature-specific wrapper is no longer treated as an exact shared export merely because its name ends in the same primitive name.
| Package | Current posture |
|---|---|
@decantr/cli 3.11.4 | Primary changed-UI and local workflow surface |
@decantr/verifier 3.11.4 | Primary authority and evidence engine |
@decantr/mcp-server 3.11.5 | Stable eight-tool agent integration surface |
@decantr/core 3.10.0 | Supported graph and execution foundation |
@decantr/essence-spec | Supported contract foundation |
@decantr/content | Supported policy and reference foundation |
@decantr/registry | Legacy 3.x compatibility facade |
@decantr/css | Legacy optional adapter |
@decantr/telemetry | Optional compatibility package |
@decantr/vite-plugin | Experimental; outside the primary reliability layer |
The MCP server preserves exactly eight public tools: decantr_project, decantr_contract, decantr_context, decantr_graph, decantr_registry, decantr_verify, decantr_repair, and decantr_contract_write.
Decantr does not currently claim that it materially improves frontier-model outcomes. That causal claim is governed by a separate, unfinished, predeclared research program. Deterministic product qualification and shipped availability do not substitute for paired model evidence or independent human review.
Read the frontier-model lift research program and 4.0 entry criteria for the complete gates and current limitations.
Requires Node.js >=20.19.0 and pnpm >=9.
pnpm install
pnpm build pnpm test pnpm qualification:3-11:changes pnpm benchmark:3-10:validate
Paid research execution is not implied by product release validation. It requires explicit budget approval, configured provider credentials, frozen treatment artifacts, sealed evaluators, and independent review.
Historical programs, audits, benchmarks, and release notes remain available as evidence of what was proposed or shipped at that time. They do not override active references or convert regression evidence into a model-lift result.
MIT. Test-corpus repositories retain their own licenses and are not redistributed by Decantr.