Cometwork MCP: connect AI agents to a shared workspace

Connect to a workspace

Open your Cometwork workspace or invitation link. Take control, then open Settings → Agent access.
Create an expiring credential. Begin with workspace:read, activity:read, and files:read. Copy the credential when it appears; it is shown once.
Configure your agent's remote MCP client with the endpoint and an Authorization: Bearer <credential> header. Use Streamable HTTP.
Connect, list tools, and call workspace_status to verify the bound workspace. Revoke access from Agent access when finished.

Hosted endpoint: https://cometwork.com/api/mcp. On a self-hosted instance, use https://YOUR-INSTANCE/api/mcp. Settings shows the endpoint for the instance you are using.

A workspace link identifies the workspace for people. It does not authorize an external agent. MCP credentials are separately scoped, bound to one workspace, hashed at rest, expiring, and revocable.

Generic configuration example

Client configuration formats differ. For clients that accept mcpServers with URL and headers:

{
  "mcpServers": {
    "cometwork": {
      "url": "https://cometwork.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <credential>"
      }
    }
  }
}

Connect Hermes Agent

Hermes documents remote HTTP MCP servers with URL and headers. Add this entry under mcp_servers in ~/.hermes/config.yaml, replacing the credential and instance URL as needed:

mcp_servers:
  cometwork:
    url: "https://cometwork.com/api/mcp"
    headers:
      Authorization: "Bearer <credential>"

Follow Hermes's official MCP documentation to reload or restart the client. This recipe follows its documented configuration; a live Hermes-to-Cometwork connection has not yet been verified.

Grok Bot

Grok Bot's official guide confirms support for Cursor MCP servers, plugins, and skills. Use the Cometwork endpoint and bearer credential with a custom remote MCP connection if your client exposes header configuration. Grok Bot's cloud computer needs a publicly reachable HTTPS instance.

Its plugin connection guide describes installing and authenticating plugins. Cometwork is not yet a verified Grok Bot marketplace plugin; an OAuth-only connection dialog cannot use this manual bearer setup. We have not run a signed-in Grok Bot acceptance test.

Instinct and Muse

Instinct is currently available through private access; its public site does not document a remote MCP setup. Multiple products use the name Muse. Until the specific client and its configuration are verified, use the generic connection requirements below.

Other clients

Use an agent client that supports remote Streamable HTTP MCP and custom bearer authorization headers. OAuth-only or local-stdio-only clients need additional integration support; the current endpoint uses manually issued credentials. Never paste credentials into a public workspace link.

Tools and permissions

Tool	Required scope	Purpose
`workspace_status`	workspace:read	Workspace details and control holder
`workspace_activity`	activity:read	Recent agent activity
`files_list`, `files_read`	files:read	Permitted directories and files
`request_control`, `release_control`	control:request	Acquire or release the control lease
`files_write`	files:write + control lease	Write a permitted file
`run_command`	commands:run + control lease	Execute a command in the agent workspace
`branches_list`	branches:read	List branches in the workspace lineage
`branch_create`, `branch_discard`, `branch_promote`	branches:write + control lease	Create, discard, or keep an isolated review branch
`branch_compare`, `review_requests`	review:read	Compare a branch or list review requests
`checkpoints_list`	checkpoints:read	List saved checkpoint metadata without VM bytes
`checkpoint_create`	checkpoints:write + control lease	Label the latest saved checkpoint
`checkpoint_restore`	workspace:restore + control lease	Create an isolated branch from a saved checkpoint

For mutations, grant control:request and the needed write or command scope. The human controller must release control before the agent calls request_control. Release control after work completes.

In local compute mode, file tools access the server-side agent sandbox, not the browser VM filesystem. Review operational limitations and privacy and data paths.

Self-hosted instances and troubleshooting

Serve the frontend and /api on the same HTTPS origin. Configure CORS_ALLOWED_ORIGINS on the API with your exact browser origin, such as https://work.example.org. Native agent clients normally omit the Origin header.

401: check the bearer header and whether the credential expired or was revoked.
403: verify that the browser Origin is explicitly allowed.
Permission denied: issue a credential with the required scope.
Control required: have the controller release control, then call request_control.

Documentation for agents

Read the plain-text documentation index or the Cometwork capability manifest. The manifest is a Cometwork-specific reference, not a universal MCP auto-install standard. Discover live tool schemas through MCP tools/list after authenticating.