# landing-connect-mcp — Add what your agents already do to OpenWork; your team runs it in OpenWork

The section leads with the user's existing agent life: skills, MCPs, and
commands from Claude Code or Cursor move into OpenWork as-is and get shared
org-wide. Teammates run them inside the OpenWork app (mini app-UI mock, like
the enterprise showcase); developers can also point their own agent at the
org's MCP server — which requires a free OpenWork account, so the connect row
carries a sign-up path. No protocol/tool-name jargon anywhere.

1. Further down the OpenWork landing page, the pitch is personal: already doing it in your agent? The skills and MCPs you run in Claude Code or Cursor can be added to OpenWork and shared with your whole team.

2. On the left, my agent's terminal — I ask it to share my setup with my OpenWork org, and it finds the granola MCP, my meeting-brief skill, and a review-pr command, shipping them to the team in one link.

3. Next to it, OpenWork itself: a teammate just types what they need — a brief for tomorrow's Acme call — and OpenWork picks up the exact skills and connections I shared.

4. The run unfolds in plain sight — Granola notes queried, the meeting-brief skill executed — and the brief lands with three talking points, no setup on their side at all.

5. Below, I choose Codex or ChatGPT Desktop alongside the other agents. Codex gives me its native command, while either desktop option opens the MCP connections screen and copies the OpenWork server URL for me.

6. The same choices appear in the docs, with an honest distinction between guided desktop setup and true one-click installs. I sign in once, pick my org, and my team's tools appear.
