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

# Installation

> Add the Nikiwa MCP server to Claude, ChatGPT, OpenClaw, or any other MCP client.

Add the Nikiwa MCP server to your client of choice. The endpoint is the same everywhere:

```
https://pro-api.nikiwa.com/mcp
```

Interactive clients authenticate with [OAuth](/mcp/connect-oauth): you sign in once and approve a consent screen. Headless and self-hosted agents use an [API key](/mcp/api-keys) instead.

## One-command install

The fastest path is the official [nikiwa-skills](https://github.com/L3galblock/nikiwa-skills) package.

<Tabs>
  <Tab title="Claude Code plugin">
    Registers the MCP server and the setup skill in one step:

    ```
    /plugin marketplace add L3galblock/nikiwa-skills
    /plugin install nikiwa@nikiwa
    ```

    On first use, Claude Code prompts you to sign in to your Nikiwa account via OAuth.
  </Tab>

  <Tab title="Any agent (skills CLI)">
    Installs the `nikiwa-setup` skill for whichever agent you use. The skill then walks your agent through adding and authenticating the server:

    ```bash theme={null}
    npx skills add L3galblock/nikiwa-skills
    ```
  </Tab>
</Tabs>

Prefer to configure your client by hand? Use the per-client instructions below.

## Pick your client

<Tabs>
  <Tab title="Claude.ai & Desktop">
    1. Open **Settings → Connectors → Add custom connector**.
    2. Name: `Nikiwa`
    3. URL: `https://pro-api.nikiwa.com/mcp`
    4. Click **Add**, then **Connect** to open the Nikiwa login and consent screen.

    <Note>
      Claude Desktop's `claude_desktop_config.json` does not accept remote `url` servers directly. Use the Connectors UI above.
    </Note>
  </Tab>

  <Tab title="Claude Code">
    The [plugin](#one-command-install) above handles this for you. To add the server manually instead:

    1. Open your terminal.
    2. Add the server:
       ```bash theme={null}
       claude mcp add --transport http nikiwa https://pro-api.nikiwa.com/mcp
       ```
       Add `--scope user` to make it available in all your projects.
    3. This triggers an OAuth flow to connect Claude Code to your Nikiwa account.
    4. If authentication doesn't start automatically, run `/mcp` inside Claude Code, select **nikiwa**, and choose **Authenticate**.
  </Tab>

  <Tab title="ChatGPT">
    1. Enable **Settings → Apps & Connectors → Advanced → Developer mode**.
    2. Add a connector with MCP server URL `https://pro-api.nikiwa.com/mcp`.
    3. Choose **OAuth** as the authentication method and complete the Nikiwa login.
  </Tab>

  <Tab title="OpenClaw">
    On the host running your OpenClaw gateway:

    ```bash theme={null}
    openclaw mcp set nikiwa '{"url":"https://pro-api.nikiwa.com/mcp","transport":"streamable-http"}'
    ```

    OpenClaw typically runs headless on a server, so authenticate with an [API key](/mcp/api-keys) rather than OAuth. Create one at [nikiwa.com](https://nikiwa.com) under profile → **MCP Keys**, and pass it as a header:

    ```bash theme={null}
    openclaw mcp set nikiwa '{"url":"https://pro-api.nikiwa.com/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer nkw_live_YOUR_KEY"}}'
    ```
  </Tab>

  <Tab title="Other self-hosted agents">
    NanoClaw, ZeroClaw, and similar self-hosted assistants run headless, so use an [API key](/mcp/api-keys) rather than OAuth.

    If the agent supports remote MCP servers natively, point it at `https://pro-api.nikiwa.com/mcp` (streamable HTTP) with the header `Authorization: Bearer nkw_live_YOUR_KEY`.

    If it only speaks stdio, bridge with `mcp-remote` (requires Node.js):

    ```json theme={null}
    {
      "mcpServers": {
        "nikiwa": {
          "command": "npx",
          "args": [
            "-y", "mcp-remote", "https://pro-api.nikiwa.com/mcp",
            "--header", "Authorization: Bearer ${NIKIWA_API_KEY}"
          ],
          "env": {
            "NIKIWA_API_KEY": "nkw_live_YOUR_KEY"
          }
        }
      }
    }
    ```
  </Tab>
</Tabs>

## Verify

Ask your agent:

> "Resolve vitalik.eth and check its wallet risk score"

If it calls `resolve_ens` and `get_wallet_risk_score` and returns data, you're connected. See the full [tool catalog](/mcp/tools) for what else you can ask.

## Troubleshooting

* **401 or an auth loop**: re-run your client's authenticate flow. For API keys, check the header is exactly `Authorization: Bearer nkw_live_...` and the key hasn't been revoked.
* **"API Subscription Required"**: you need an active plan at [nikiwa.com](https://nikiwa.com).
* **Browser doesn't open**: your client may not support OAuth for remote MCP servers. Use an [API key](/mcp/api-keys) or the `mcp-remote` bridge, which handles OAuth itself.
* **Connection refused / 404**: verify the URL is exactly `https://pro-api.nikiwa.com/mcp` (note the `/mcp` path).