Connecting MCP Clients
Cloud Harness MCP provides two distinct connection lanes over Streamable HTTP MCP:
AI CLIENT
│
┌──────────────────┴──────────────────┐
▼ ▼
Managed OAuth Lane Static API Key Lane
https://harness.zuey.me/mcp https://api.harness.zuey.me/mcp
│ │
Browser OAuth SSO Static Header Bearer
(GitHub / Google via Access) Authorization: Bearer <key>
│ │
• Claude Desktop / ChatGPT Custom App • Cursor / Claude Code
• Codex App (Loopback OAuth) • Non-interactive CLI scriptsProtocol Lane Comparison
| Feature | Managed OAuth Lane | Static API Key Lane |
|---|---|---|
| Public URL | https://harness.zuey.me/mcp | https://api.harness.zuey.me/mcp |
| Authentication | Cloudflare Access OAuth | Dashboard-managed API Key |
| Header | Access JWT Cookie / Bearer | Authorization: Bearer <api-key> |
| Target Clients | ChatGPT, Web App Connectors | Cursor, Claude Code, Codex, Antigravity |
| Key Expiry | Session bound | 1–3,650 days (configurable, approximately 10 years) |
| Max Keys per Identity | N/A | 10 active keys |
Local Stdio Mode
In addition to remote Streamable HTTP, Cloud Harness MCP can run locally over stdio against a selected folder:
bash
cloud-harness-mcp --transport stdio --workspace /absolute/path/to/projectLocal mode exposes the full tool surface directly to the local folder with host-user authority. Closing the workspace terminates processes without deleting the project folder.
Managing API Keys
- Log into the Operator Dashboard at
https://harness.zuey.me/dashboard. - Navigate to API Keys in the sidebar.
- Click Generate New Key, specify an expiry (1–3,650 days, approximately 10 years) and label.
- Copy the revealed key immediately. Store it securely in your local environment or credential vault.
One-Time Display
API keys are shown exactly once upon creation and cannot be recovered from the database. If lost, revoke the old key and create a new one.
Supported AI Clients
Select your AI coding tool for specific setup instructions: