Bring your agent into the workplace.
One sentence gives your agent the exact connection steps. You approve the organization and a bounded read grant in the browser. Write access stays a second decision.
Fetch https://kept.do/workplace/agent-setup/prompt.md and follow its instructions to connect Kept Workplace to this agent over MCP.
Four checkable steps
One remote MCP server at https://mcp.enterprise.kept.do/mcp. Use native OAuth with no static Authorization header.
OAuth opens in the browser. The person signs in, chooses the organization, and reviews the requested permissions.
The agent calls a Workplace read tool and reports the protocol result. A tool call, not a narrated claim, proves the connection works.
When task management is authorized, read the shared queue, claim the work, renew the lease, and finish with evidence.
One organization, five read surfaces
The Sealed Brief for the organization approved in OAuth · Plans and their sections · Workplace documents · Todos and their derived status · The Morning Paper
Personal Kept notes, tasks, calendar, goals, or habits · Another Workplace organization · Organization memory or the imported corpus without separate read scopes · Email, browser tabs, device files, or cloud drives through this connection · Any Workplace row through a write tool until write scopes are approved
When task management is authorized, read the shared queue, claim the work, renew the lease, and finish with evidence.
The same commands your agent reads
Claude, Claude Code, ChatGPT, Codex, and Cursor all use the shared connection facts from the detailed reference.
Claude on claude.ai
https://mcp.enterprise.kept.do/mcpOpen https://claude.ai/customize/connectors, add a custom connector, and paste the server URL. Leave OAuth client credentials empty. A Workplace owner may need to add the connector for a Team or Enterprise organization.
Claude Code
claude mcp add --transport http kept-workplace https://mcp.enterprise.kept.do/mcpThen, in the session:
/mcpAdd the server with OAuth and no Authorization header. Then use /mcp and let the person finish sign-in and consent in the browser.
ChatGPT
https://mcp.enterprise.kept.do/mcpEnable Developer mode, create an app for the server URL, and let ChatGPT discover OAuth. The registered callback is https://chatgpt.com/connector_platform_oauth_redirect; the person does not paste it into chat.
Codex CLI
codex mcp add --url https://mcp.enterprise.kept.do/mcp kept_workplaceFor reading Workplace:
codex mcp login --scopes brief:read,plans:read,docs:read,todos:read,paper:read,spaces:read,projects:read,members:read,comments:read,files:read,inbox:read,offline_access kept_workplaceFor managing Workplace tasks:
codex mcp login --scopes brief:read,plans:read,docs:read,todos:read,paper:read,spaces:read,projects:read,members:read,comments:read,files:read,inbox:read,memory:read,memory:write,plans:write,docs:write,todos:write,corpus:read,spaces:write,projects:write,comments:write,files:write,inbox:write,offline_access kept_workplaceCodex add may begin OAuth immediately with all advertised scopes. For bounded read access, merge a URL-only config entry first, then run the read login. For requested task management, use the full grant. Both include offline_access for refresh.
Cursor
"kept-workplace": { "url": "https://mcp.enterprise.kept.do/mcp" }Add this entry under "mcpServers" in .cursor/mcp.json or the global ~/.cursor/mcp.json, show the diff to the person, then restart Cursor if it asks.