Access gate for AI coding harnesses (DSH plugin + Claude Code hook): per-directory deny/read/full, roster groups, audit log, model-facing tools with owner-approved widening.

Wassette: A security-oriented runtime that runs WebAssembly Components via MCP

Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authe

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

Connects AI agents to a user's mailbox with OAuth-scoped permissions, enabling email sending, inbox management, verification-email capture for tests, and migration from Resend.

Enables AI assistants to answer natural-language questions about environmental monitoring stations, returning real-time readings, hourly time-series, and combined station overviews. Supports per-user account binding and OAuth 2.1 authorization so each user only sees stations within their own permissions.

Server-grade gateway that turns DeepSeek Harness into a multi-tenant platform: remote access + auto HTTPS, subuser permissions & quotas, sandbox enforcement, encrypted auth, audit log.

Enables AI clients to securely access and manage IMAP mailboxes through OAuth-protected tools for searching, reading, organizing, flagging, moving, and deleting emails or folders, with optional write permissions.

Exposes explicitly approved local Windows stdio and loopback HTTP MCP backends through a single OAuth-protected remote HTTPS MCP endpoint, letting a mobile AI client invoke whitelisted tools with namespacing, PKCE-based authorization, and per-tool permissions.

Turns a Frappe site into a remote MCP server that AI clients such as Claude can sign in to with OAuth and use curated, task-level tools registered by installed apps. Every call runs as the signed-in user with that user's permissions, with schema-checked arguments and rollback on failure.

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.