Skip to main content
The OpenWork MCP server (OpenWork Connect) enables OpenCode 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 OpenCode 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 this MCP entry to your opencode.json file:
  2. Authenticate the server:
  3. Finish the browser sign-in, then choose the organization OpenCode should use.
If OpenCode runs on a remote machine or SSH host, follow Connect OpenWork MCP from a remote machine.

​
Switch organizations

Log out, then authenticate again and pick the organization you want in the browser:
OpenCode is the verified OpenWork Connect client. Native remote MCP OAuth passed end-to-end implementation testing.

​
What you can ask

  • “Which OpenWork organization am I connected to?”
  • “Add omar@example.com to my organization.”
  • “Create a skill that writes weekly status reports and share it with my whole organization.”
  • “Find the Q3 launch page in Notion and summarize it.”

​
What’s next