oioxo-mcp weekly downloads statistics

OIOXO — cut your AI bill up to ~90%, and code privately from the terminal

Your AI tools read far more of your code than they need — and you pay for every word.

OIOXO fixes that from one command-line tool. It does two things:

1. Makes Copilot, Cursor & Claude up to ~90% cheaper. It sits between your project and your AI tools and hands them only the small, relevant slice — instead of letting them read whole files. Same answers, a fraction of the cost.
2. Codes for you, privately. oioxo code "<task>" plans, edits, and checks the work right in your repo — using your own key or a local model — so nothing leaves your machine. See Code in your terminal.

Up to ~90% fewer words per question (measured on a real codebase). A question that would cost ~50,000 words can come back as ~5,000 — same answer, a fraction of the cost.

Quick start

npm install -g oioxo-mcp

oioxo login   # connect your OIOXO account (opens the browser)
oioxo init    # wire OIOXO into the agents in this project

Restart your agent. From the next prompt on, it calls OIOXO before reading files.

Prefer zero terminal? Install the OIOXO VS Code extension — it wires every workspace automatically and shows your live savings in the status bar.

Code in your terminal — oioxo code

OIOXO isn't only a context engine for other agents — it's a coding agent in its own right. oioxo code plans, edits, and verifies on your machine (runs your tests / typecheck), then shows the diff and asks before writing any file.

<p align="center"><img src="https://aradsoftca.github.io/OIOXO/assets/terminal.gif" alt="oioxo code — reads only the slice it needs, plans, writes, runs your tests, then asks before writing" width="640"></p> <p align="center">_{<em>A real <code>oioxo code</code> run — reads ~5,000 words not 50,000, writes, runs your tests, and asks before it touches a file.</em>}</p>

# with your own key (BYOK) — the capsule means even a frontier model reads ~10× fewer tokens
OPENAI_API_KEY=…    oioxo code "add a --json flag to the status command"
ANTHROPIC_API_KEY=… oioxo code "fix the failing test" --verify "npm test"

# local Ollama — private, zero API tokens, nothing leaves your machine
OIOXO_PROVIDER=ollama OIOXO_MODEL=qwen2.5-coder oioxo code "add input validation to the signup form"

• Verified, not vibes — every change runs through your tests/typecheck on a shadow copy; a red result is fed back and repaired. Your real files are touched only after you approve the diff.
• Bring any model — OpenAI, Anthropic, Groq, Mistral, Together, local Ollama, or any OpenAI-compatible base (OIOXO_PROVIDER / OIOXO_BASE_URL / OIOXO_MODEL / OIOXO_API_KEY).
• Or fully local, no key — point it at Ollama (OIOXO_PROVIDER=ollama OIOXO_MODEL=qwen2.5-coder) and nothing leaves your machine. Or run the built-in on-device coder with oioxo code --local (open model via llama.cpp; one-time npm i -g node-llama-cpp) — no key, nothing uploaded.

Flags: --verify "<cmd>" (override the test command) · --yes (apply without the prompt) · --max-iters N · --local (built-in on-device coder, no key — one-time npm i -g node-llama-cpp).

Let your devices build together

<p align="center"><img src="https://aradsoftca.github.io/OIOXO/assets/mesh.gif" alt="Compute Mesh — your phone borrows your laptop's power over Wi-Fi" width="620"></p>

Put two of your own devices on the same Wi-Fi and they work as one — this machine can lend its power to another device's build (so your phone or a thin laptop builds on this machine's GPU), or borrow power the other way. Start it with oioxo invite (or oioxo join); pairing is just a short code (a QR or a string), with nothing going through our servers. Lend power and you earn free coding time for it. (Feature name: Compute Mesh.)

Why developers use it

• 💸 Your AI costs drop by up to ~90% — Copilot premium requests, Claude limits, and API keys all last several times longer.
• ⚡ Better answers, too — focused context beats 50k words of noise. Your AI gets the exact code in play, plus the parts it actually depends on.
• 🔒 100% on your device — your code is read and searched locally, never uploaded. Only the amount you saved is counted.
• 🪄 One command — init finds Claude Code, VS Code/Copilot, Cursor, Windsurf, Gemini CLI and Codex, and sets them up without touching your other tools.

How it works (for you)

1. Point it at your project — oioxo init wires your agents in one command.
2. Ask your agent normally — it calls OIOXO first, gets just the relevant slice, and answers.
3. Watch the savings add up — oioxo-mcp status shows tokens saved; nothing about your code leaves your machine.

Tools your agent gets

Tool	What it does
get_context	The minimal relevant slice of the codebase for any task
get_impact	Blast radius — everything a change might break, before refactoring
get_skeleton	A file's full API surface at ~10% of its token cost
remember / recall	Durable project memory in .oioxo/, shared with the OIOXO IDEs

Commands

# Code
oioxo code "<task>"        code in this repo: capsule-grounded, verified, then asks
                           before writing (--verify "<cmd>" · --yes · --max-iters · --local)
                           --local runs the built-in on-device coder, no key

# Account
oioxo login | logout       connect / disconnect your OIOXO account
oioxo whoami | usage        who you're signed in as · your saved-token allowance
oioxo status               plan, savings and on-device index stats…