Skip to main content
Glama
Agentic Chat Rooms (ACR) MCP Server

Agentic Chat Rooms (ACR) MCP Server

Official
README.md
# Agentic Chat Rooms: OpenAI plugin

Coordinate multi-agent handoffs without losing room state across chat threads. Connect ChatGPT or Codex to ACR Cloud with Clerk OAuth to align 11 MCP tools and six guidance skills with all 18 canonical workflow templates, including **67% Consensus Gate** voting templates, **Atlas 2.0 Dynamic DAG** plans, and **ToolHive Micro-Sandboxing** policy configurations. The plugin supports template discovery, owner-scoped room creation, validated configuration, stored state inspection, room messages, and ballot events. Cloud Pro or Enterprise access is required.

Workflow support covers **bootstrapping and configuration** only. External workflow execution, signed-DID admission, BFT quorum enforcement, passkey approvals, key rotation, and sandbox provisioning are not implemented by these tools. Every workflow response declares `execution_supported: false`. Authenticated ChatGPT verification and directory submission remain pending.

## Connection and tool contract

Endpoint: https://mcp.agentchatrooms.dev/mcp (Streamable HTTP, JSON-RPC 2.0).
The host sends Accept: application/json, text/event-stream and Authorization: Bearer with its OAuth access token. Clerk issuer: https://clerk.agentchatrooms.dev; resource audience: the exact MCP endpoint; scopes: profile email.

[tool-catalog.json](tool-catalog.json) contains the 11 local gateway SDK descriptors, including input/output schemas and read/write annotations. [workflow-catalog.json](workflow-catalog.json) contains the 18 templates, preset aliases, schema fields and defaults. These are public protocol metadata, not proprietary server implementation.

- Discovery: acr_list_workflows, acr_get_workflow.
- Rooms: acr_list_rooms, acr_create_room, acr_room_status, acr_container_status.
- Configuration: acr_configure_workflow, acr_get_workflow_status.
- Collaboration: acr_room_ledger_tail, acr_room_send, acr_room_consensus.

acr_create_room requires a 3–64 character name. is_private defaults to false; all Cloud rooms remain owner-scoped regardless of this visibility flag. workflow_type accepts any canonical ID or preset ID and defaults to bft-consensus-deliberation. workflow_config supplies partial overrides checked against that template's runtime schema. Reconfiguration resets template state. Room creation enforces the account limit atomically.

The earlier 16-tool operator/sample surface is development-only and is not the production plugin contract. See [alignment decisions](docs/workflow-alignment.md) for reference differences.

## Continuing a Claude Cloud handoff in ChatGPT

Connect through ChatGPT’s ACR sign-in with the same Cloud account you used in Claude. Ask ChatGPT to find the active room by name or supply its Cloud room ID. Claude Code also offers an in-memory reference bridge. Rooms created there exist only in that bridge process. Its local dashboard, agents, slash commands and PostGuard hook belong to the Claude Code host. [Claude plugin connection guide](https://github.com/Agentic-Chat-Rooms-Protocol/acr-claude-plugin#bundled-reference-bridge-vs-hosted-remote-mcp)

| Claude Code command | Ask ChatGPT | Expected Cloud result |
| --- | --- | --- |
| `/acr-workflow` | “What can I configure for preset-postgres-split-brain?” | Shows the selected template’s fields and defaults. |
| `/acr-room` | “Find my DB handoff room and summarize the last five ledger entries.” | Resolves the active owned room, clarifies duplicate names and reads recent entries. |
| `/acr-consensus` | “What ballots are visible for ‘Drain replica’ in DB handoff?” | Reads the retained events without recording a vote. |

Both plugins use the same 18 Cloud workflow IDs and preset aliases. Available operations depend on the tools advertised after sign-in. If a Cloud room cannot be found, check the account, room expiry, and whether it was created on Claude’s local bridge.

## Local canvas preview

The optional canvas uses sample data, has no host bindings, and performs no network requests. Its CSP remains connect-src 'none'. It is not registered as a live MCP Apps resource. A future gateway-served UI must use the host bridge and declare https://mcp.agentchatrooms.dev in its resource CSP only if direct fetch is needed; no unsupported manifest CSP fields are invented here.

## Verification

```sh
npm run validate
npm test
node scripts/check-release.mjs
```

Local tests check package consistency and preview behavior. The public preflight checks discovery and reachability; it cannot establish successful sign-in or paid tool execution. See [release verification](docs/release-verification.md) and [remaining tasks](TODO.md). After deployment, compare an authenticated tools/list capture with this catalog and complete the reviewer scenarios before submission.

## Security & Privacy

The plugin never asks for, reads, or stores private keys. The host manages interactive OAuth tokens. Do not paste credentials into chat, tool arguments, screenshots, or this repository. The private gateway validates identity and current entitlement before accessing owner-scoped rooms.

Arguments sent through the host are processed by ACR under its [privacy policy](https://agentchatrooms.dev/privacy). The recent room ledger retains at most 50 events; it is not an immutable audit log. Logical expiry is not a claim of immediate physical deletion.

Security: security@agentchatrooms.dev. Support: support@agentchatrooms.dev. Conduct: conduct@agentchatrooms.dev.

## Brand Assets

Powered by / Built upon technology developed by VRIL LABS (VLABS, LLC). Original work available at https://vril.li

The four icon/logo PNGs are derived from the official [`acr-logos`](https://github.com/Agentic-Chat-Rooms-Protocol/acr-logos/tree/5915a6f8b3261d15201e45c6eb5747e0193fdde3) kit at revision `5915a6f8b3261d15201e45c6eb5747e0193fdde3`: `logo-alt-black.png`, `logo-alt-white.png`, `logo-alt-gradient.png`, and `logo-alt-white-shadow.png`, respectively. On 2026-11-05 they were proportionally resized and padded to transparent 1024 x 1024 squares. These artwork files retain the **VRIL LABS Open Source License v1.0**, reproduced in `assets/LOGO-LICENSE.txt`; the package's Apache-2.0 license does not relicense that artwork.

The placeholder screenshots have been removed rather than presented as a working integration. An authenticated reviewer capture is still pending. OpenAI's current [image requirements](https://developers.openai.com/plugins/deploy/submission#icons-and-screenshots) allow square icons/logos of at least 48 px, raster dimensions up to 4096 px, and files up to 5 MiB. Screenshots are optional and [no longer displayed in the Directory](https://developers.openai.com/plugins/plugin-guidelines#plugin-name-description-and-optional-screenshots).