Integrations / Claude Code
Bring your team's graph into Claude Code.
Deep context + write-back for every coding session. Oynix runs as an MCP server, so Claude Code answers from your team's real code, decisions and docs.
$ oynix mcp setup --client claudePrerequisites
- The Oynix CLI installed and signed in (oynix login).
- Claude Code installed, with MCP support enabled.
Setup steps
Install the Oynix CLI
Everything Oynix does runs from one small command-line tool on your own machine — there's nothing to deploy or host. Open your terminal (Terminal on Mac, PowerShell on Windows) and paste this in to install it:
$ curl -fsSL https://get.oynix.dev | sh- Don't have a terminal open? On Mac press ⌘+Space, type "Terminal", hit Enter.
- Paste the line, press Enter, and wait for it to finish — that's it.
- Check it installed: run oynix --version (it should print a version number).
Sign in
Tell Oynix who you are. This opens your browser to sign in with GitHub and links this computer to your workspace — it's how your edits, decisions and presence get attributed to you.
$ oynix login- Run the command; your browser opens automatically.
- Approve the sign-in with GitHub, then return to the terminal.
- If your team uses a workspace key, paste it when asked (a teammate with the master key issues it).
Generate the config
Run setup for Claude Code. Oynix prints a small config snippet (already filled in for you) and tells you exactly where it goes — your secret stays a reference, never written into the file.
$ oynix mcp setup --client claude- Run the command in your terminal.
- Copy the snippet it prints out (it includes the copy button here too).
Paste it into the config
Open .mcp.json (project root) — or run claude mcp add and paste the snippet, then save.
- Where: .mcp.json (project root) — or run claude mcp add.
- If the file already lists other MCP servers, add ours alongside them (don't delete theirs).
- If the file doesn't exist yet, create it and paste the snippet in.
Restart & connect
Fully quit and re-open Claude Code so it loads the new server. That's it — it now answers from your team's real graph.
Check it works
Open Claude Code and ask it something about your codebase — for example, "how does login work?". If it answers using your actual code and decisions, you're connected.
- Make sure Claude Code was fully restarted after you pasted the config.
- Not answering from your code? Re-open the config file and confirm the snippet is there and saved.
What your agent gets
Context
The whole knowledge graph — code, decisions, docs — as live context.
Why
The decisions and discussions behind the code it's editing.
Write-back
Each session's output is captured back into the graph for next time.