# System Manager MCP agent onboarding

Canonical Streamable HTTP endpoint: `https://mcp.zing.kr/mcp`

이 주소에 접속한 것만으로는 MCP 사용 권한이 부여되지 않습니다. 먼저 사용
요청을 생성하고 사용자에게 권한 프로필 검토·승인을 요청한 뒤에만 연결을
완료할 수 있습니다.

This public relay contains no API key, password, private key, internal system
document, or runtime binary. Every agent must create its own registration
request and receive owner approval before claiming a one-time client key.

## Connection flow

1. Download the setup template listed in the relay manifest: Codex
   `https://mcp.zing.kr/setup/codex.toml`, VS Code
   `https://mcp.zing.kr/setup/vscode.json`, Claude-compatible
   `https://mcp.zing.kr/setup/claude.md`, or vendor-neutral
   `https://mcp.zing.kr/setup/generic.json`.
2. POST a registration request to `https://mcp.zing.kr/mcp/register`.
3. Keep the returned request token in an owner-only local file.
4. Wait for the owner to approve a general, professional, full, or custom profile.
5. POST the token once to `https://mcp.zing.kr/mcp/register/<request_id>/claim`.
6. Store the returned key as `SM_MCP_KEY`; never paste it into chat or source control.
7. Connect to `https://mcp.zing.kr/mcp` and call `initialize`, then `tools/list`.
8. If permitted, read `system-manager://bootstrap/context` and synchronize the
   approved Exchange cursor.

## Environment contract

```dotenv
SM_MCP_URL=https://mcp.zing.kr/mcp
SM_MCP_KEY=<APPROVED_CLIENT_KEY>
```

The legacy `https://ai.zing.kr/mcp` endpoint remains available for existing
clients, but new agents should use the canonical endpoint above.  A client UI
that only supports OAuth and cannot send a private Bearer header is not directly
compatible with this relay yet; do not place the key in a URL query parameter.