Authorize
Sign in through Clerk and approve the MCP connection.
606 Engineering Assurance connection
Bring your own AI. Connect the engineering control plane.
Your coding agent performs repository work with the model access and tools you already control. 606 supplies private coordination, evidence custody, and explicit report state.
Codex
Add the remote MCP server.
Run these commands in a trusted terminal, then complete browser-based authorization through Clerk.
codex mcp add cyber-ai --url https://mcp.606intelligence.com/mcp
codex mcp login cyber-aicyber-ai is the temporary technical connection alias, not the final public product name. Start a new Codex task after installation if the tool inventory does not refresh.
First assessment
Ask for the outcome, not a skill filename.
The connected agent discovers the public service capabilities. 606 returns bounded work from the request and observed project context without exposing proprietary engine logic.
“Use 606 Engineering Assurance to assess this repository and make the current release professionally ready. Preserve existing behavior and show the evidence for every conclusion.”
Describe the outcome
State the repository, release goal, constraints, and workflow rules.
Continue the loop
The agent receives bounded work until the report reaches an explicit state.
SECURITY / CLIENT
Never paste credentials into a prompt.
Authentication happens through OAuth. 606 Engineering Assurance does not request a model-provider API key. The connected agent still operates with the local authority you grant it, so consequential repository and infrastructure changes remain subject to review.