Skip to main content
OpenWork reaches most apps through MCP: an admin adds the app’s MCP server as a connector. 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

For the full list of actions in each service, see 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.

​
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 and MCP server compatibility.

​
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.

Talk to our team

Book a 30-minute call, or email team@openworklabs.com.