Add skills, approved service connections, and supported MCP servers to Work on Mac.
On a compatible Gab AI Mac build, open Settings → Plugins. This Settings section is available on Mac; web, iOS, and Android do not offer it. Work requires Plus. If a feature is missing, check the installed Mac version and the message shown by the app.
Browse the catalog, inspect a package, and install it. Portable skill packages add reusable instructions for work such as research, writing, meeting notes, or spreadsheet review. A package labeled (Browser) needs approved browser access on the Mac. Installation by itself does not authorize files, apps, websites, or accounts.
Where a catalog package offers Connect, choose it, finish the provider’s authorization in your browser, and return to check the connection status before choosing Use in Work. Providers such as Gmail, Google Drive, Google Calendar, GitHub, GitLab, Notion, and Slack depend on server configuration and your eligibility. Available actions depend on the service and the permissions you approved. A browser workflow and a connected-account package are different ways of reaching a service.
Choose Add MCP server, enter a server name and its public HTTPS Streamable HTTP MCP URL, and choose Connect server. An optional access token is supported only when the backend enables token connections; the form explains when it is unavailable. Tokens are encrypted in your Gab AI account and sent to that server. Tool inputs are shared with the server when used, so add a server only if you trust it.
The custom form does not support local commands, localhost or private-network servers, arbitrary headers, URL credentials, legacy SSE-only endpoints, or custom OAuth sign-in. Use the catalog’s Connect flow for supported OAuth services. Server availability and tool discovery do not guarantee that every action will succeed; Work action approvals still apply.
You can update, disable, or remove a package and disconnect an account in Settings. New Work tasks use the selected instruction snapshot. Existing tasks keep their original instructions, while service calls still require a valid connection. Disconnecting stops subsequent service access; it cannot undo an action already accepted by the provider. Folder, browser, and app permissions are managed separately.