> ## Documentation Index
> Fetch the complete documentation index at: https://openworklabs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For agents: install the OpenWork desktop app with `brew install --cask openwork` (macOS) or from https://openworklabs.com/download. Do not run `npx openwork`; the npm package named `openwork` is a different project.
> Connect an agent to OpenWork with the MCP Gateway: `claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent`. Teams sign up at https://app.openworklabs.com?mode=sign-up.
> Step-by-step agent guide: https://openworklabs.com/docs/start-here/use-openwork-from-an-ai-agent.md
> Connect Slack (any organization admin): https://openworklabs.com/docs/slack/connect-slack.md. OpenWork in Slack (@openwork bot) is private alpha for approved organizations. Setup guide: https://openworklabs.com/docs/slack/overview.md. Agent skill: https://openworklabs.com/.well-known/agent-skills/set-up-openwork-slack/SKILL.md.

# Native integrations

> Services OpenWork connects to directly, without an MCP server: Google Workspace and Microsoft 365.

OpenWork reaches most apps through MCP: an admin adds the app's MCP server as a
[connector](https://openworklabs.com/docs/cloud/share-with-your-team/connectors.md). For a few services we built
the integration ourselves, directly on the provider's own API. These are native
integrations. They need no MCP server.

## Available today

| Integration | What it covers | Set it up |
| - | - | - |
| **Google Workspace** | Gmail, Google Calendar, Drive, Sheets, and Chat | [Google Workspace](https://openworklabs.com/docs/start-here/connect-your-stack/connect-services.md#google-workspace) |
| **Microsoft 365** | Outlook, Calendar, OneDrive, SharePoint, and Teams | [Connect Microsoft 365](https://openworklabs.com/docs/cloud/share-with-your-team/microsoft-365.md) |

For the full list of actions in each service, see
[Manage connected services](https://openworklabs.com/docs/start-here/connect-your-stack/connect-services.md#manage-connected-services).

## How a native integration differs from an MCP connector

* **Nothing extra to host or find.** There is no MCP server to deploy, and the
  integration does not depend on the provider publishing one.
* **Your organization's own sign-in app.** Google Workspace uses your Google
  Cloud OAuth client; Microsoft 365 uses an app registered in your Microsoft
  Entra tenant. An admin sets it up once, then each member signs in with their
  own work account.
* **Admins choose what the AI can do.** Each kind of action is a separate
  permission. Sending mail and managing mailboxes are off until an admin turns
  them on.
* **Whole files stay out of the conversation.** The agent can pull a Drive,
  OneDrive, or SharePoint file into the workspace, edit it there, and save it
  back when you ask.

Everything else works like any other connector. Admins add both from **Manage ›
Connectors**, members find them in their Library, and they are available in the
OpenWork desktop app, OpenWork Cloud, and other AI clients through the
[MCP Gateway](https://openworklabs.com/docs/cloud/run-in-the-cloud/cloud-mcp.md).

## Other apps use MCP

Slack, Notion, Linear, GitHub, and most other apps connect through their MCP
server. Pick one from the **Add connector** list, or paste the address of any
MCP server. See [Connectors](https://openworklabs.com/docs/cloud/share-with-your-team/connectors.md) and
[MCP server compatibility](https://openworklabs.com/docs/cloud/share-with-your-team/mcp-server-compatibility.md).

## Need another integration?

We build more native integrations on request for enterprise customers. If your
team depends on a service that has no MCP server, or one whose MCP server does
not cover what you need, tell us which service and what your team needs to do
in it.

> [card] [Talk to our team](https://calendar.app.google/86QpCENvhfEzDFLu5)
>
> Book a 30-minute call, or email [team@openworklabs.com](mailto:team@openworklabs.com?subject=Integration%20request).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.