Operate and build your business from the terminal.

Excellent ships an MCP server and an excellent-mcp CLI, so the Claude, Codex, or Cursor you already run can drive your workspace — under the same ship/verify gate the app enforces.

Get ExcellentRead the docs

One install line · off by default · reverse it any time

zsh
$ excellent-mcp install-skills✓ registered MCP server 'excellent' with Claude Code + Codex✓ installed the Excellent skills as slash commands✓ launcher at ~/.local/bin/excellent-mcp✓ wired the ship/verify hooks

One tool belt for your whole operation — least privilege at the terminal.

Excellent exposes about 165 MCP tools across work, CRM, hiring, agents, and sync. Every mutating tool carries a declarative authz descriptor, checked at the MCP dispatch and CLI perimeter against the capability graph — so even terminal access runs under least privilege, not root.

Work

task_listtask_createtask_update

Customers

lead_createopportunity_movecomm_sendsequence_enroll

Hiring

job_createapplication_movescorecard_submitcandidate_search

Agents & goals

goal_creategoal_reconcileworker_run_listplay_action_propose

Schema

entity_createnote_addtag_applyurn_resolveworkspace_list

Optimization

loop_createvariant_proposepromotion_review

Sync

sync_statussync_now

Integrations

connection_connectintegration_provider_listrecord_list

Every mutating tool carries an authz descriptor — a 165-tool manifest applied centrally to the registry; a call without a grant is denied before the handler runs.

Real CLI

Check who you are, ship, and verify — without opening the app.

excellent-mcp mirrors the whole UI. Identity is derived from your session, so a terminal agent is a genuine second party: it can approve work it didn't ship, and nothing else.

{ ok: false, reason: "self-verification-blocked" }
zsh
$ excellent-mcp agent idclaude-8df093 · your stable identity$ excellent-mcp agent ship-checkclear to ship — claim held on #42$ excellent-mcp review approve 42 --note "verified"✓ #42 → done (verifier ≠ shipper)$ excellent-mcp goal new "Keep the review queue empty" --role verifier✓ goal created · role verifier · on-demand

or the agent calls tools directly: task_list { status: "review" } → lead_create { name: "Dana Ruiz", … }

Your client

Bring the agent you already run — Claude Code, Codex, or Cursor.

excellent-mcp install-skills registers the server (named excellent) with Claude Code, and with Codex if it's on your PATH; any MCP-aware client — Cursor, Gemini, Grok — connects the same way. It also installs the Excellent skills as slash commands and drops a launcher at ~/.local/bin/excellent-mcp.

registered as the excellent MCP server

One tool belt

Move a deal, or ship a pull request — same tools, same gate.

One plane operates the workspace: opportunity_move, task_update, comm_send. The other develops this monorepo: the coding agent edits live source, runs pnpm verify, and lands the change through todo → review → done. Both cross the identical ship/verify gate — a different identity must verify before anything is done.

Plane 1

Operate the workspace

opportunity_movetask_updatecomm_send

ship / verify
gate

Plane 2

Develop the monorepo

edit live sourcepnpm verifytodo → review → done
zsh
$ excellent-mcp agent convergeverifier · drain review → approve #41, reject #43 (tests red)shipper  · ship todo #44, fix bounced #43verifier · approve #43, approve #44queue clean — 0 review, 0 todo

One install line. Off by default. Reversible.

Run it from a source checkout; install-skills wires the ship/verify hooks so every terminal session respects the gate. Inspect state with excellent-mcp status; undo everything with excellent-mcp uninstall-skills.

A local file you own

The CLI and the stdio server run on your machine against the same local SQLite the app reads. There is no cloud endpoint — nothing phones home.

Least-privilege on every mutation

Every mutating tool carries a declarative authz descriptor, checked against the capability graph at the MCP dispatch and CLI perimeter — not root, even from the terminal.

The gate applies to terminal work

Your identity is derived from the session, so a terminal agent is a genuine second party: it can verify work it didn't ship, and it can't approve its own.

Off by default, reversible

Autopilot and every agent role stay off until you enable them. Inspect state with excellent-mcp status; undo the whole install with uninstall-skills.

excellent-mcp uninstall-skills

Keep going.

The terminal drives the same product every one of these surfaces reads from.

Agents

The supervised roles that ship and verify under the gate.

Work

The board the terminal drives — same rows, three views.

Integrations

Pull outside tools into the one database you own.

Docs → The MCP server

Install it, register the server, and connect your host.

Bring your terminal to your business.

Install once, register the excellent server, and drive your whole operation from the shell you already live in.

Get ExcellentRead the docs