Connectivity with a durable center

Bring your clients. Keep one work record.

MCP, ACP, and API paths connect different hosts to the same authorized project board.

MCP connects tools. Pursers coordinates work.

A connection does not grant a role. Central still checks the principal, board membership, capability, and current lease for every protected action.

Seats can use different hosts without fragmenting tickets or review evidence.

Headers, display labels, prompts, and local UI state never create board authority.

Check the linked release notes and host guide before changing a production configuration.

Released

Connect any authorized MCP client to Central using the documented endpoint and token-file flow.

Core server contract

Released

A stdio relay and curated prompts bring board work into Zed's Agent Panel.

pursers-client 0.1.1+

Released

pursers-acp exposes the board, create, watch, evidence, and answer workflows.

pursers-acp 0.1.0+

Documented

Named seats use the same authenticated board contract through their supported MCP configuration.

CLI host guides

Documented

Non-MCP workers can use the authenticated API contract while preserving board roles and evidence.

Central API contract

Planned

A small cross-host skill bundle is being designed and is not part of the current release yet.

Experience program

Permission prompts, restricted modes, background behavior, and notification support vary by host.