Connect the OpenWork MCP Gateway (https://api.openworklabs.com/mcp/agent) to Claude Code, Codex, Gemini CLI, Cursor, VS Code, Claude Desktop, or ChatGPT so the agent can use the user's OpenWork organization skills, plugins, and connections.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Server URL: https://api.openworklabs.com/mcp/agent
Transport: Streamable HTTP. Auth: OAuth (PKCE, dynamic client registration); the client opens a browser for sign-in. No API key is needed.
The user needs an OpenWork Cloud account. If they don't have one, send them to https://app.openworklabs.com?mode=sign-up first.
Use the command for the client you are running in. If an openwork entry already exists, don't add a duplicate; sign in with the existing one.
Claude Code:
claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent
# add `-s user` to make it available in every project
Codex:
codex mcp add openwork --url https://api.openworklabs.com/mcp/agent
codex mcp login openwork
Gemini CLI:
gemini mcp add --transport http openwork https://api.openworklabs.com/mcp/agent
OpenCode:
opencode mcp add openwork --url https://api.openworklabs.com/mcp/agent
opencode mcp auth openwork
Cursor, VS Code, Claude Desktop, ChatGPT, Windsurf, Zed: add https://api.openworklabs.com/mcp/agent as a remote MCP server. Per-client steps: https://openworklabs.com/docs/start-here/connect-openwork-mcp
/mcp, select openwork, and authenticate.codex mcp login openwork opens the browser./mcp auth openwork.opencode mcp auth openwork opens the browser.The user signs in and picks their organization. The organization is pinned to the token; to switch, log out of the openwork server and sign in again.
claude mcp list (or the client's equivalent) shows openwork.search_capabilities and execute_capability tools.Don't claim the connection works until step 3 passes.
invalid_grant: log out of openwork in the client and sign in again.https://api.<your-den-web-host>/mcp/agent.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add a new feature, put work behind a feature flag, roll something out (per organization, for everyone, cloud or self-hosted), revert or kill a feature, or make a big change to existing behavior such as a new engine. Use BEFORE writing the feature code, and when finishing or removing a rollout.
日本語の概要は準備中です。原文の説明を表示しています。
Local OpenWork Electron browser automation with CDP. Use when driving a local Electron dev app, browser_list, browser_snapshot, browser_eval, composer automation, or local UI smoke tests.
日本語の概要は準備中です。原文の説明を表示しています。
Flag customer, prospect, partner, or outside-person identities in the diff. Reported in the Warden security summary.
日本語の概要は準備中です。原文の説明を表示しています。
Screen a pull request from an outside contributor for hidden, obfuscated, or supply-chain-risky changes before any of its code runs.
日本語の概要は準備中です。原文の説明を表示しています。
Create an OpenCode plugin for OpenWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
日本語の概要は準備中です。原文の説明を表示しています。
Daytona CLI setup, sandbox debugging, keep a sandbox alive, secrets volume, snapshot refresh. Use when Daytona itself is the problem, not for running tests (see run-tests).
日本語の概要は準備中です。原文の説明を表示しています。