# Cometwork > Cometwork is a collaborative computer for people and AI agents. ## Public documentation - https://cometwork.com/agents.html — static MCP guide, Hermes configuration, self-hosting, and tool permissions - https://cometwork.com/mcp-capabilities.json — Cometwork-specific capability manifest - https://cometwork.com/mcp — connect an external agent through Streamable HTTP MCP - https://cometwork.com/specs — technical architecture and bounded claims - https://cometwork.com/realities — operational limitations and tradeoffs - https://cometwork.com/privacy — privacy and data paths ## MCP compatibility Cometwork exposes a generic, scoped MCP server at https://cometwork.com/api/mcp. Credentials are created inside workspace Settings → Agent access. Workspace session links are not MCP credentials. Tools cover workspace status, agent activity, permitted file reads/listing, shared mini-app reads/creation/updates, control requests, file writes, commands, review branches, saved checkpoints, branch comparisons, and review requests. Writes, commands, branch mutations, and checkpoint labeling require both explicit scopes and the authoritative control lease. Checkpoint restore creates an isolated review branch; replacing the live browser VM remains an interactive-client operation. Verified October 29, 2026: MCP TypeScript SDK 1.30.0 over Streamable HTTP, discovery of all 21 registered tools and scoped file/app/branch/control/revocation operations against an isolated development API. Two-browser testing reproduced a split-arrival defect, applied a live source fix, synchronized arrivals, retained state after refresh, rejected stale state writes, and revoked the connected client. Backend checks covered scopes, workspace isolation, encryption and control epoch fencing. A signed-in Grok Bot client session was not connected in this run. ## Self-hosted instances Use /api/mcp on the instance origin, not necessarily cometwork.com. Settings shows the instance endpoint. Configure CORS_ALLOWED_ORIGINS for browser clients. ## Client setup Hermes documents remote HTTP MCP with URL and bearer headers; see the agent guide for a configuration recipe. End-to-end named-client compatibility is not yet tested. OAuth-only and stdio-only clients require additional integration support. ## Registry and named clients - https://cometwork.com/server.json — official MCP Registry submission format - https://cometwork.com/agents.html#grokbot — Grok Bot documentation and connection requirements Grok Bot officially documents Cursor MCP support. A signed-in Grok Bot acceptance test and marketplace installation are not yet verified. Instinct is private access; its public site does not document MCP configuration. Muse requires product identification. Runtime note: Local MCP files target the server agent sandbox, not the browser Local VM or shared server Terminal. Cloud tools target /home/oai/share only when Cloud is configured and actually starts. See /docs#files for import/export and save boundaries. ## Runnable check-in rehearsal - https://cometwork.com/examples/check-in.html — isolated sample guests; open in a shared workspace or download the app source for Replit - https://cometwork.com/mcp#shared-apps — shared app workflow and tool instructions Use miniapps_list and miniapps_read with miniapps:read. Use miniapps_create and miniapps_update with miniapps:write and the control lease. These tools update the app on the shared desktop live; they do not access the browser VM filesystem or change a separately hosted Replit backend. Reset sample arrivals inside the app.