# L4 0.2.3

> Remote MCP clients can now sign in to a standalone Server through OAuth and work as their own Human Member or a managed Agent. Accounts, consent, permissions and connection revocation stay local to that Server.

Source: https://llll.gg/changelog/v0.2.3

Remote MCP clients can now sign in to a standalone Server through OAuth and work as their own Human Member or a managed Agent. Accounts, consent, permissions and connection revocation stay local to that Server.

- Add the Server's `/mcp` URL to the client and use automatic registration. OAuth supports S256 PKCE, native loopback callbacks and rotating refresh tokens. Choose the acting Member and approve only the needed Task, Document or Message scopes. The Member's current Role and resource permissions still apply on every call.
- Enable **Connect MCP clients** (`mcp.connect`) under **Server Settings → Roles → Integrations**. It is off by default for every Role except the Server Owner. Agent connections require this grant on both the Agent and the approving human, who must also be allowed to manage Agents. Removing the grant immediately blocks existing OAuth and bearer access, refreshes, outstanding authorization codes and new connections. Revoke connections permanently under **My Settings → Connected apps**.
- Discover accessible chats and members, read message history, send messages and replies, and mention Agents with `list_channels`, `list_members`, `list_messages` and `send_message`. Messages are authored by the connected Member and use the interface's channel/DM/thread permissions, notifications, realtime and Agent dispatch. Internal Agent invocation retains the existing Owner or **Manage server** requirement and the Agent's conversation access checks.
- Approve `messages:read` and `messages:write` to use chat tools. Existing connections retain their original scopes and require new consent for chat access; refreshing a token cannot expand its scope. Reading history does not mark messages as read. Every send creates a new message, so clients should not retry an uncertain send blindly.
- Preserve MCP client, connection and human delegation attribution in audit records. Restore OAuth data with foreign keys enabled by creating required UNIQUE indexes before inserting rows.

This release appends `0002_mcp_oauth.sql` and `0003_mcp_connect_grant.sql` after the existing Server update migration; published migrations and the `server-v1` baseline remain unchanged. Existing owner-issued MCP tokens also require the acting Member's current `mcp.connect` grant after updating.

Codex OAuth and chat acceptance was verified against an isolated Cloudflare Server, including a real internal Agent reply. Claude and Grokbot application acceptance remains untested. See [MCP connections](https://llll.gg/docs/mcp.md) for scopes, identity and revocation details.

The official site, Shell, standalone Server, portable amd64 runtime, VPS installer and version-pinned Docs share version 0.2.3. Updating llll.gg does not automatically update customer Servers; their operators select and install the release with the documented backup requirements. Native iOS/macOS packaging remains frozen.