# org-mcp-agent-config-demo — An admin publishes a team connection from chat, and everyone gets a clean way in

Cast: Alex (org admin) and Jordan (member), both in the OpenWork desktop app
against a real Den stack. The external tool is played by the mock MCP server
(protocol-identical to Notion). This is Path A (classical) from
evals/org-mcp-agent-config-ux.md: the agent creates and configures the
connection, and members are handed the existing connect experience — a link
to Your Connections on the web, and the same card in desktop Extensions.
Path B (the connect card rendered inline in chat) is mapped in the same doc
and not narrated here.

1. Alex does not open a dashboard. He just tells his agent to publish the team knowledge base connection for the whole company, with everyone signing in as themselves — and the agent finds the right capability on its own.

2. The agent sets it up and reports back like a colleague: it names the connection it created, and it hands Alex the exact link where teammates connect their own account on the web — ready to paste into Slack.

3. Alex asks who can use it, and the agent reads the access back: everyone in the org, each with their own sign-in. Governance you can ask about in plain language.

4. Jordan opens her own OpenWork and there it is — the connection her admin created in a chat window, waiting in Extensions with Connect your account. Same card, same flow she already knows.

5. And when Jordan asks her own agent to publish a connection, it politely declines: that needs an admin. The agent's power is your role, nothing more.
