Try demoDownload
Developers

Developers

Two surfaces, one page: the Control Center product you integrate with (its MCP tool server, CLI and Docker images) and this website itself, which is built to be read by agents — llms.txt, per-page markdown, an OpenAPI document and a docs MCP server.

Quickstart

Run the server, then point any MCP client at it:

  • Install the desktop app or grab the standalone cc_server binary from GitHub Releases (cc_server-<version>-macos-arm64.tar.gz, -linux-x64.tar.gz, -windows-x64.zip), or run the Docker image ghcr.io/samuelalev/cc-server with -p 9030:9030.
  • Start it: cc_server (listens on 127.0.0.1:9030 by default).
  • Connect a client: the MCP endpoint is http://127.0.0.1:9030/mcp (Streamable HTTP).

The quick start tutorial walks the same path through the app, and Run a headless server covers Docker, TLS, tunnels and pairing.

The MCP server

Control Center registers 103 typed tools and serves them over the Model Context Protocol on the main cc_server listener — no separate port:

  • POST /mcp — Streamable HTTP transport; the one clients speak.
  • GET /sse — server-sent notification stream.
  • DELETE /mcp — end a session.

The surface is on by default and binds loopback; serving beyond the host requires a bearer token (fail-closed by design). Every workspace-scoped tool requires a workspace_id — there is no implicit "current workspace". Use the MCP server has the client configuration, and MCP tools is the full tool catalog.

CLI and containers

cc_server is scriptable: every setting takes a CLI flag or an environment variable (flag wins), and subcommands cover device pairing (cc_server pair), Google Calendar connect and self-update (cc_server update). cc_server CLI is the complete reference.

Each release publishes four GHCR images — cc-server, cc-webapp, cc-remote and cc-signaling-server — with a compose file in the headless-server guide.

This site, for agents

usectrl.dev itself is agent-readable. Every page below is live:

  • llms.txt — the curated site index; llms-full.txt — the whole site as one file, including when-to-use guidance.
  • Markdown twins — send Accept: text/markdown on any page, or append .md to its URL (/index.md, /manual/quick-start.md, …).
  • openapi.json — an OpenAPI 3.1 description of this site's endpoints, with typed responses and operation ids.
  • /.well-known/api-catalog — an RFC 9727 catalog of the APIs on this origin, each with its description and docs. Every page also carries Link headers for it (rel="api-catalog", service-desc, service-doc, describedby), so nothing here needs HTML parsing to find.
  • /.well-known/mcp/server-card.json — the MCP server card for the docs server above: who it is, which URLs it answers on and which protocol versions it speaks.
  • /.well-known/agent-skills/index.json — published skills, each a SKILL.md with a SHA-256 digest over the exact bytes served, so you can verify what you loaded.
  • /.well-known/mcp — a Streamable HTTP MCP server (also at /mcp) exposing this site's pages as tools: list_pages, get_page_markdown, search_pages.
  • Sitemap, RSS and structured JSON error envelopes for missed routes.

Source code

Everything above is MIT-licensed at github.com/SamuelAlev/control-center — app, server, fleet worker, web and phone clients, signaling relay, and this site (in docs/). Issues and reproductions: the tracker.