Two ways. The skill teaches Claude Code, Codex or any assistant the API, the relay protocol and the byte-exact encryption recipe, with code for Swift, Rust, Python, TypeScript, Kotlin and Flutter. The MCP server lets the assistant register your application, read its key, create test users and inspect devices and connections — without leaving the editor.
Download and unzip into your assistant's skills folder. For Claude Code that is ~/.claude/skills/
(or .claude/skills/ inside the project). Codex, Cursor and others read the same Markdown: point them at
SKILL.md.
curl -L https://cybsin.com/skill.zip -o cybsin-skill.zip
unzip cybsin-skill.zip -d ~/.claude/skills/
# → ~/.claude/skills/cybsin/SKILL.md + references/
Or read it online: /skill/SKILL.md, api.md, crypto.md, swift.md, rust.md, python.md, typescript.md, kotlin.md, flutter.md.
"Add CybSin to this app so the iPhone and the Mac
versions can pair with a code and sync notes.
Use the cybsin skill."
The skill makes the assistant: register the application (or ask you for the key), send X-App-Key on every call,
scope users to the app, implement pairing with code + QR, run the X25519 → HKDF → ChaCha20-Poly1305 handshake exactly, show
the SAS fingerprint, handle 402 payment_required gracefully, and report device identity so your key stays yours.
Remote MCP over Streamable HTTP at https://cybsin.com/mcp. Authenticate with a developer token from
Console → Account → API tokens.
# Claude Code
claude mcp add --transport http cybsin https://cybsin.com/mcp \
--header "Authorization: Bearer cs_dev_…"
# Codex (~/.codex/config.toml)
[mcp_servers.cybsin]
url = "https://cybsin.com/mcp"
http_headers = { Authorization = "Bearer cs_dev_…" }
# Cursor / Windsurf / Claude Desktop (mcp.json)
{ "mcpServers": { "cybsin": {
"url": "https://cybsin.com/mcp",
"headers": { "Authorization": "Bearer cs_dev_…" } } } }
# stdio-only clients
npx mcp-remote https://cybsin.com/mcp --header "Authorization: Bearer cs_dev_…"
cybsin_integration_guide | skill + platform code (works without a token) |
cybsin_create_app | register an app, get its key, declare bundle ids |
cybsin_list_apps / cybsin_get_app | keys, plan state, counts |
cybsin_update_app / cybsin_rotate_key | identity binding, rotation |
cybsin_create_test_user | credentials to pair two devices during development |
cybsin_list_devices / cybsin_list_connections / cybsin_list_events | who connected, from where, how much |
cybsin_billing | plan, price, checkout link or invoice instructions |
Tool calls that change billing stop at the checkout link: a human completes the payment.
You: "Make the phone and desktop versions talk through CybSin."
Assistant: calls cybsin_create_app with your bundle ids, stores the key in the app's config, reads cybsin_integration_guide for Swift and Rust.
Assistant: implements sign-in, pairing (code + QR), the E2E handshake and your protocol inside the tunnel, then creates a test user and tells you how to pair the two builds.