Skip to main content
The OpenWork MCP server (OpenWork Connect) enables Codex 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 Codex 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:
  2. Log in and finish the browser sign-in:
In the Codex desktop app, open codex://settings/connections and paste the server URL there instead.

​
Switch organizations

Log out, then log in again and choose the organization you want:
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. Codex 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?”
  • “Add omar@example.com to my organization.”
  • “Search my org’s capabilities for calendar tools, then list tomorrow’s events.”
  • “Create a skill that writes weekly status reports and share it with my whole organization.”

​
What’s next