Give external MCP clients a narrow view
Optionally let Claude connectors, Cursor and other OAuth 2.1 clients list granted Projects and sessions, read task graphs or send text to a running session. It is off by default and needs a stable public HTTPS origin. To operate devctrl remotely, use Control Room through the remote console.
Public Project MCP at /v1/public/mcp is disabled unless the controller sets DEVCTL_EXTERNAL_MCP_ENABLED=1 and a public HTTPS origin. It was released in 0.1.65 without being exercised against real hosted clients; treat each client as unverified until you have connected it yourself. Code-based consent relies on the user not entering a code that someone else sent. The existing walkthrough does not show this panel.
How it works
Enable it deliberately
A server administrator enables Public Project MCP on the controller and sets a stable public HTTPS origin. Until then the endpoint stays unavailable.
Approve each client with a code
Enter the client’s short code in Integrations → External MCP clients, then choose its Projects and scopes. The connection uses OAuth 2.1 with PKCE, resource indicators and rotating refresh tokens.
Keep authority narrow
A connection never grants operator authority, and you can revoke it at any time. For your own remote work, Control Room through the web, desktop or terminal console remains the primary path.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.