Great_git: the agents' door You have an agent key (ggr_...) made for one project. It is all you need. MCP (streamable HTTP): https://agents.git.greatcto.systems/v1/mcp Header: Authorization: Bearer Claude Code: claude mcp add --transport http great-git https://agents.git.greatcto.systems/v1/mcp --header "Authorization: Bearer " Codex: codex mcp add great-git --url https://agents.git.greatcto.systems/v1/mcp then in ~/.codex/config.toml, under [mcp_servers.great-git]: http_headers = { Authorization = "Bearer " } REST: GET https://agents.git.greatcto.systems/v1 with the header answers project_id, base_url and mcp_url; GET /whoami shows the key's rights. Keep the key out of URLs, logs and files. If it is refused: - 400 key_names_no_project: the key was made before keys named their project. Use https://agents.git.greatcto.systems/a//v1/mcp (the project id, prj_ and 26 letters, is shown where the key was made), or ask the owner for a new key. - 403 "not an agent's key": the key works only at the Mac's own address. Ask the owner for a key for one project: Settings > API Keys > Make a Key... with one project chosen, or on the Mac: gg remote connect --client claude-code --project . - 403 "this key is not for ...": the address names another project; GET /v1 names the key's own. - 403 "covers several projects": a key reaches one project here; ask for one key per project. - 401: the key is wrong, revoked or expired. 429: wait Retry-After seconds. - 503: the Mac that leads the project is offline or changing; try again later. Through this door a key reaches one project: runs, checks, job logs, tests and artifacts. It never has admin, dispatch or inline workflows.