OYNIX

Integrations / Any tool via MCP

Connect anything that speaks MCP.

If a tool exposes an MCP server, Oynix can ingest from it — bring your own source without waiting for a built-in connector.

$ oynix connect other

Prerequisites

  • An MCP server for the tool you want to connect.
  • The Oynix CLI installed and signed in (oynix login).

Setup steps

01

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).
02

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).
03

Point at the MCP server

Run the command and choose the MCP option, then give Oynix the MCP server to read from.

$ oynix connect other
04

Authorize

Provide whatever credentials that MCP server needs — Oynix passes them through.

05

Sync anytime

Oynix ingests what the MCP server exposes and links it to your code.

$ oynix connectors sync
06

Check it worked

List your connectors to confirm Any tool via MCP shows up and is syncing. Once it's synced, ask the graph a question that should now have an answer from Any tool via MCP.

$ oynix connectors
  • You should see Any tool via MCP listed as "connected".
  • Try it: oynix ask "what did we decide about …?" — answers can now draw on Any tool via MCP.

What gets indexed

Your source

Whatever the MCP server exposes, ingested as documents.

Links to code

Linked — by meaning — to the code it relates to.

One graph

It lands in the same graph as everything else.