Skip to main content
Local workspace setup. Custom MCP servers are supported without an OpenWork Cloud account, so this path stays free and local to the current workspace. For a connection managed and assigned by your organization, use OpenWork Cloud connectors under Manage › Connectors.
Use this guide only when you need a custom or local MCP server that is not available through OpenWork Connect. For Gmail, Google Calendar, Google Drive, Slack, Notion, Linear, and other managed services, follow Connect your services. Connecting a custom app with OpenWork takes four clicks.
  • In the desktop app, open Settings › Library, expand Advanced settings, then click Add workspace MCP.
Library page with Advanced settings expanded, showing the Add workspace MCP button
Enter an App name and a Server URL, then click Add App. The MCP is added to the current workspace.
Add workspace MCP dialog with app name, server URL, and OAuth optionsIf the server requires OAuth, expand OAuth on this device before adding it.
This setup is intended for servers that support dynamic OAuth client registration.
OAuth approval page for MCP server
Complete the provider’s OAuth approval flow in your browser. It should redirect back to OpenWork. If a custom MCP needs behavior OpenWork does not support, open an issue.

​
Troubleshooting

Some MCP servers do not support dynamic client registration. If the server gives you a pre-registered OAuth client ID and client secret, add it in Add workspace MCP under OAuth on this device (OAuth client ID and OAuth client secret).
Workspace MCPs are local to you. To share an MCP App with the organization as a dashboard, add it in OpenWork Cloud under Manage › Connectors and see Dashboards.
Error when MCP server does not support dynamic client registration