RELATED 01
OpenConnector
Self-hosted auth gateway that runs prebuilt Actions across 1,000+ SaaS apps over MCP
6.2kGitHub stars
2.4k/wknpm downloads
83popularity score
OpenWork MCP Gateway
One hosted OAuth endpoint for the skills, plugins, workflows and connections an OpenWork org shares
Official · Different AI TypeScript Remote (hosted) · Streamable HTTP ProductivityAI and MLDeveloper tools
40 popularity score ★ 24k
Connect your client
Remote (hosted)
Add in one click
Opens the app, which asks before it adds the server.
Or add it by command or config
Claude Codeterminal; then run /mcp and select openwork
claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agentCodexterminal
codex mcp add openwork --url https://api.openworklabs.com/mcp/agent
codex mcp login openworkVS Codeterminal; then MCP: List Servers > openwork > Start Server
code --add-mcp '{"name":"openwork","type":"http","url":"https://api.openworklabs.com/mcp/agent"}'CursorAdd to Cursor link, or paste the URL as a remote MCP server
{
"mcpServers": {
"openwork-gateway": {
"url": "https://api.openworklabs.com/mcp/agent"
}
}
}ChatGPTSettings > MCP servers, paste the URL
https://api.openworklabs.com/mcp/agentClaude (desktop and web)Settings > Connectors > Add custom connector, paste the URL
https://api.openworklabs.com/mcp/agentopencodeterminal
opencode mcp add openwork --url https://api.openworklabs.com/mcp/agent
opencode mcp auth openworkGemini CLIterminal; then /mcp auth openwork in gemini
gemini mcp add --transport http openwork https://api.openworklabs.com/mcp/agentWhat it does
OpenWork MCP Gateway is the remote MCP endpoint of OpenWork Den, the team control plane behind the OpenWork desktop app. You add one URL to your coding agent, sign in through the browser and pick an organization. The agent can then use whatever that organization has shared with you: skills (SKILL.md files), plugins, saved Workflows, Google Workspace and Microsoft 365 actions, and the external MCP servers your team has connected.
It keeps the client's tool list short. Rather than exposing every connected service as its own tool, it gives the agent a keyword search over the capabilities you can use and a tool that runs one of them by its exact name. Alongside these are direct tools for listing, reading and creating skills, testing small sandboxed JavaScript workflows, and building interactive MCP Apps. Each App is then served as its own MCP server under /mcp/agent/connections/<appId>.
The documentation lists only search_capabilities and execute_capability, and the README lists four tools. The gateway's source (ee/apps/den-api/src/mcp/agent.ts) registers more: execute_capability_script, the skill tools, and the App builder tools, which appear when App servers are enabled for the deployment. What each person can reach follows their organization membership, role, policies and exposure allowlists, and is checked again on every call.
What it needs
An OpenWork account (a free one can be created at sign-in) and membership in an OpenWork organization that has shared skills, plugins or connections. You also need an MCP client that supports remote Streamable HTTP with OAuth. Codex needs `codex mcp login openwork` after adding the server, OpenCode needs `opencode mcp auth openwork`, and Gemini CLI needs `/mcp auth openwork`. Windsurf and Zed connect through mcp-remote. A self-hosted Den serves the gateway at its own API origin, and production use of Den requires an OpenWork subscription.
Limits
OpenCode is the only client its makers have verified end to end. They describe Claude Code, Claude Desktop, Codex, Cursor, VS Code, ChatGPT, Windsurf, Zed and Gemini CLI as setup only. The organization is fixed in the token, so switching means logging out and signing in again. Access tokens expire after 45 minutes, and refresh grants lapse after 30 days without use. Every call to an external provider's tool needs the mcp:write scope, even for tools that call themselves read-only (an mcp:read-only token must be reauthorized). The gateway returns 429 with Retry-After when rate-limited. It never exposes admin-only routes, webhooks, API-key management or endpoints that return credentials.
Who it suits
It suits teams that already run OpenWork or OpenWork Den and want the skills and connections they share to show up in Claude Code, Codex, Cursor or another agent without configuring each service in each client. It does little for someone with no OpenWork organization, since everything it offers comes from what an org shares. It runs on OpenWork's servers unless you self-host Den, so people who want a server that runs entirely on their own machine should connect the individual MCP servers directly. Pick OpenCode if you want the one client its makers have verified.
Tools 11
search_capabilities- Keyword search over the connection actions, saved Workflows and skills shared with you
execute_capability- Runs one capability by the exact name a search returned
execute_capability_script- Tests a sandboxed JavaScript function that calls discovered capabilities, for use as a saved Workflow
list_skills- Lists the skills available to you
get_skill- Returns one skill's SKILL.md by its name
create_skill- Saves a new skill into a plugin (needs the mcp:write scope)
prepare_app- Generates a starter MCP App wired to the tools it will call
create_app- Publishes an MCP App into a plugin as its own MCP server
read_app- Returns an App's source for editing
update_app- Publishes a new revision of an App at the same URL
save_artifact_view- Saves a view of Workflow results when App building is not enabled