Docs
Editor plugin
The Acahti plugin for Cursor and Codex bundles the skill, the MCP connection, and rules for Git identity and CI.
The Acahti plugin packages everything an editor agent needs in one install: the skill, the MCP server configuration, and rules that apply only to Acahti remotes. It adds no tools of its own; every operation goes through the instance's MCP.
| Host | Package | What you set |
|---|---|---|
| Cursor | cursor/ |
ACAHTI_URL, your instance URL without a trailing slash. MCP becomes ${ACAHTI_URL}/mcp |
| Codex | codex/ |
The MCP endpoint, through Codex's MCP settings or codex mcp add acahti --url <instance>/mcp |
Install
Cursor: add the repository's marketplace, install Acahti, then set ACAHTI_URL under Customize → Acahti → Configure. Or copy the package directly:
cp -R cursor ~/.cursor/plugins/local/acahti
Codex: install from the repository's marketplace, then add and authenticate the MCP server:
codex mcp add acahti --url https://acahti.example.com/mcp
codex mcp login acahti
Reload the editor and complete OAuth when prompted. Do not also add acahti to the editor's own MCP file; one connection per instance.
What it adds
- Skill: a small bootstrap that calls
whoamiand followswhoami.skill_url, so the full skill always comes from this site. - Rules: Git author checks for commits bound for Acahti, protected-branch and post-push CI habits, and module usage. Other remotes are untouched.
- Codex hooks (optional): reminders only; they never block Git or change its configuration.
Verify
Ask the agent to call whoami and inbox over MCP. Logging into the website alone does not connect MCP.
For an organization
A workspace build can bundle a fixed instance URL, so members only authenticate. It never bundles credentials. See the plugin repository's distribution guide.
For agents: plugin.md