Attenza
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AttenzaCreate an intervention request for the release"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Attenza integrations
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 |
| OAuth and MCP contract tested by Attenza; repository validation | Complete a real Cursor intervention round trip |
Cursor Agent Plugin | Root | 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.
Related MCP server: Brainbase MCP
What every folder is for
Path | Why it exists |
Cursor-specific setup and testing notes | |
GrokBot publication status and next steps | |
The single canonical instruction set that teaches an agent when to pause and how to resume | |
The dependency-free | |
Synthetic intervention payloads for testing | |
The public JSON shape accepted by the CLI | |
Repository boundary, manifest, and secret-leak checks | |
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/mcpThe 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_IDThe 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 checkSee CONTRIBUTING.md and SECURITY.md before contributing.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Access Kernel's cloud-based browsers and app actions via MCP (remote HTTP + OAuth).
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Related MCP Servers
- AlicenseAqualityFmaintenanceProvides secure OAuth2-based credential management for MCP servers, allowing agents to obtain short-lived token references without exposing raw secrets.722MIT
- AlicenseNot gradedqualityBmaintenanceEnables management of Brainbase agents, components, evals, tasks, and more via a remote MCP connection with OAuth authentication.2MIT
- AlicenseNot gradedqualityBmaintenanceBridge that lets stdio-only MCP clients connect to remote MCP servers with OAuth and other auth support, enabling local clients to use remote, authorized MCP servers.24353MIT
- AlicenseNot gradedqualityAmaintenanceA spec-compliant remote MCP server with built-in OAuth 2.1 and Dynamic Client Registration, enabling Notion Custom Agents to connect via 'Sign in with OAuth' without bearer tokens. It supports SSO federation to Google and Microsoft Entra, and includes basic tools like whoami, echo, and slow_task.MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/maxhillaert/attenza-integrations'
If you have feedback or need assistance with the MCP directory API, please join our Discord server