> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trynia.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> Install Nia and configure it for your coding agent.

## Quick Install

Run a single command to install Nia:

```bash theme={null}
npx nia-wizard@latest        # npm
pnpx nia-wizard@latest       # pnpm
bunx nia-wizard@latest       # bun (fastest)
yarn dlx nia-wizard@latest   # yarn
```

This wizard will:

* Work for both new and existing users
* Create your account or log you in
* Generate your API key automatically
* Auto-detect and configure your IDE
* Get you running in under a minute

<Info>
  That's it! The wizard handles everything - just follow the prompts and you're done.
</Info>

<Warning>
  **Previously installed `nia-sync`?** The deprecated `nia-sync` package (installed via `pip` or `uv`) ships a `nia` binary that conflicts with the new CLI. Uninstall it before running the wizard:

  ```bash theme={null}
  pip uninstall nia-sync   # or: uv pip uninstall nia-sync
  ```

  Verify it's gone:

  ```bash theme={null}
  which nia   # should return nothing or point to the new CLI
  ```
</Warning>

<Accordion title="Alternative installation method">
  ```bash theme={null}
  curl -fsSL https://app.trynia.ai/cli | sh
  ```
</Accordion>

***

## Choose Your Setup

There are four ways to connect Nia to your agent. They all give you access to the same Nia platform — they just differ in how the agent talks to it.

<CardGroup cols={2}>
  <Card title="CLI" icon="terminal" href="/integrations/installation/cli">
    A standalone command-line tool for terminal-based agents and pipelines.

    * Full platform access from the shell
    * JSON output for machine parsing
    * Async jobs with streaming
    * No background processes
  </Card>

  <Card title="MCP Server" icon="server" href="/integrations/installation/mcp">
    The standard approach. Your IDE connects to Nia through the **Model Context Protocol** — either via a remote server (recommended) or a local process.

    * Native IDE support for 30+ editors
    * Automatic context management
    * Remote server option (zero dependencies)
    * Best for complex, multi-step workflows
  </Card>

  <Card title="Agent Skill" icon="bolt" href="/integrations/installation/skill">
    A lightweight alternative. Your agent reads a skill file and calls the Nia API directly — no MCP server or background process needed.

    * Single command install
    * No background processes
    * Works with any agent that supports skills
    * Lighter resource usage, sometimes faster than MCP
  </Card>

  <Card title="agentsearch" icon="magnifying-glass" href="/integrations/installation/agentsearch">
    Zero-install docs browser. One `npx` command lets your agent read any docs site through familiar Unix tools.

    * No account, no API key
    * `tree`, `cat`, `grep`, `find` over any docs URL
    * Pipe straight into Claude Code or CLAUDE.md
    * Perfect ad-hoc front door to Nia
  </Card>
</CardGroup>

<Info>
  **Not sure which to pick?** If your agent runs in the terminal (Claude Code, custom pipelines), go with the **CLI**. If your IDE natively supports MCP, go with the **MCP Server**. If you want a single skill file with no background process, try the **Agent Skill**. If you just need an agent to read external docs *right now* with zero setup, reach for **agentsearch**.
</Info>