Skip to main content
The OpenWork MCP server (OpenWork Connect) enables Claude Code to use the OpenWork capabilities your organization has made available to you: Gmail read/search, Calendar list/create, Drive search/read, Gmail draft creation, shared MCP connections such as Notion, Linear, Slack, Stripe, Exa, and Context7, shared skills, and OpenWork Cloud resources like skills, plugins, marketplaces, workers, members, roles, teams, and LLM providers. The server exposes only search_capabilities and execute_capability, so Claude Code searches what you can access and runs exact capability names instead of loading hundreds of tool definitions into context.

​
Server URL

OAuth sign-in uses your OpenWork account, and the organization you pick is pinned into the token. If you do not have an account, create a free OpenWork account.

​
Setup

  1. Add OpenWork Connect as a remote HTTP MCP server:
    Add -s user to make it available in every project.
  2. Open Claude Code and run /mcp.
  3. Select openwork, then follow the browser sign-in and choose your organization.

​
Switch organizations

Run /mcp inside Claude Code, select openwork, then clear or re-authenticate the connection. The next browser sign-in lets you pick a new organization.
This is a setup guide. These steps match OpenWork Connect’s OAuth profile: HTTPS or HTTP loopback callbacks, PKCE S256, and dynamic client registration fallback. Claude Code is listed as setup only because native proof is not complete. See the client support status table.

​
What you can ask

  • “Which OpenWork organization am I connected to?”
  • “Search my org’s capabilities for calendar tools, then list tomorrow’s events.”
  • “Assign Priya to the Sales team.”
  • “Find the Q3 launch page in Notion and summarize it.”

​
What’s next

  • Read the hub overview for OAuth, token, server exposure, and troubleshooting details.
  • Publish Notion, Linear, Slack, and other shared tools with shared MCP connections.