Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kyberis.ai/llms.txt

Use this file to discover all available pages before exploring further.

Use @kyberis-ai/mcp to connect MCP-capable agents to Kyberis tools. The setup flow uses a one-time connect token and returns a short-lived bearer credential for the MCP connection. Install the Kyberis skill as well when your agent supports skills. The skill teaches the investigation workflow; MCP provides the callable tools.

​
Prerequisites

  • Node.js 20 or newer
  • A one-time Kyberis connect token from API keys, beginning with kct_
  • A supported client: claude, codex, cursor, windsurf, or generic

​
Connect a client

npx -y @kyberis-ai/mcp connect claude --token kct_abc123
Replace claude with your client name. 
npx -y @kyberis-ai/mcp connect cursor --token kct_abc123
npx -y @kyberis-ai/mcp connect codex --token kct_abc123
npx -y @kyberis-ai/mcp connect windsurf --token kct_abc123
npx -y @kyberis-ai/mcp connect generic --token kct_abc123 --json
The command exchanges the token with Kyberis and configures supported clients by default.

​
Options

npx -y @kyberis-ai/mcp connect claude \
  --token kct_abc123 \
  --agent-label "SOC laptop Claude" \
  --api-url "https://api.kyberis.ai"
Use --dry-run when you want configuration guidance without changing local client config. 
npx -y @kyberis-ai/mcp connect windsurf --token kct_abc123 --dry-run
Use --json when you need machine-readable connection details. --json does not change local client config. 
npx -y @kyberis-ai/mcp connect generic --token kct_abc123 --json

​
Default configuration targets

For supported clients, @kyberis-ai/mcp updates the local MCP configuration by default:
ClientDefault action
ClaudeRuns claude mcp add --transport http kyberis ...
CodexUpdates ~/.codex/config.toml
CursorUpdates ~/.cursor/mcp.json
WindsurfUpdates ~/.codeium/windsurf/mcp_config.json
GenericNo default install target; use --dry-run or --json and copy the config

​
What the command returns

The setup command returns:
  • agent_id: the registered agent identity
  • mcp_url: the MCP endpoint URL
  • api_key_id: the API key bound to this agent connection
  • Authorization: Bearer <token> header for the MCP client
  • client-specific configuration for Claude, Codex, Cursor, Windsurf, or generic MCP clients

​
Token errors

Generate a new connect token from API keys when setup returns one of these conditions:
ErrorMeaning
connect_token_not_foundThe token does not exist.
connect_token_usedThe token was already exchanged.
connect_token_revokedThe token was revoked.
connect_token_expiredThe token expired.
connect_token_wrong_clientThe token was created for a different client type.

​
After connecting

Run a simple prompt in your agent: 
Use Kyberis to check API health, then resolve CVE-2024-3094 as a CVE.
The agent should call Kyberis tools through MCP and preserve request IDs in any error report.