Attenza integrations

License: MIT

The small public integration kit for Attenza. It contains only the client-side pieces needed to connect agents to Attenza: a CLI, one agent skill, one portable plugin manifest, and focused setup notes.

The Attenza application, API implementation, database, deployment, and infrastructure remain in a separate private repository.

Integration status

Integration	Available now	Currently tested	Next step
Cursor remote MCP	`mcp.json` points to the public OAuth endpoint	OAuth and MCP contract tested by Attenza; repository validation	Complete a real Cursor intervention round trip
Cursor Agent Plugin	Root `plugin.json`, MCP manifest, and polling skill form one portable package	Manifest structure and CI checks	Install locally, verify skill discovery, then submit to the marketplace
GrokBot custom connector	Shared OAuth endpoint works without a private URL	OAuth, tool discovery, intervention creation, human decision, and result retrieval tested end to end	Retain as the direct integration path
GrokBot plugin	The portable Agent Plugin adds polling and expiry behavior to the same MCP endpoint	Package validation; raw MCP round trip tested	Publish through the Cursor marketplace and verify catalog installation
Attenza CLI	Browser OAuth, create, get, wait, cancel, and token refresh	Six unit tests, clean wheel build, and isolated install	Complete one interactive OAuth and intervention smoke test

We are intentionally taking integrations one at a time. Other agent platforms are out of scope until Cursor and GrokBot are working end to end.

What every folder is for

Path	Why it exists
`integrations/cursor`	Cursor-specific setup and testing notes
`integrations/grokbot`	GrokBot publication status and next steps
`skills/attenza-intervention`	The single canonical instruction set that teaches an agent when to pause and how to resume
`src/attenza_cli`	The dependency-free `attenza` command-line client
`examples`	Synthetic intervention payloads for testing
`schemas`	The public JSON shape accepted by the CLI
`scripts`	Repository boundary, manifest, and secret-leak checks
`tests`	CLI unit tests; they do not contact a live account

At the repository root, plugin.json, mcp.json, and skills/ together are the portable Agent Plugin used by Cursor and GrokBot. Keeping them at the root means there is no second copied plugin tree and no duplicated skill. .github, mise.toml, pyproject.toml, and the policy files are ordinary public-repository maintenance files.

Public endpoint

OAuth-capable MCP clients connect to:

https://staging.attenza.io/mcp

The client discovers Attenza OAuth, opens sign-in and consent, and receives revocable user-scoped access. Do not publish API keys, OAuth tokens, authorization codes, or legacy capability URLs.

CLI

uv tool install git+https://github.com/maxhillaert/attenza-integrations.git
attenza login
attenza create examples/release-approval.json
attenza wait TASK_ID

The CLI stores its OAuth tokens only in the user's local configuration directory. Run attenza logout locally and revoke the connection in Attenza when it is no longer required.

Develop

mise install
mise run check

See CONTRIBUTING.md and SECURITY.md before contributing.

Attenza

Attenza integrations

Integration status

What every folder is for

Public endpoint

CLI

Develop

Latest Blog Posts

MCP directory API