Installation - Nikiwa

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: you sign in once and approve a consent screen. Headless and self-hosted agents use an API key instead.

One-command install

The fastest path is the official nikiwa-skills package.

Claude Code plugin
Any agent (skills CLI)

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.

Installs the nikiwa-setup skill for whichever agent you use. The skill then walks your agent through adding and authenticating the server:

npx skills add L3galblock/nikiwa-skills

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

Pick your client

Claude.ai & Desktop
Claude Code
ChatGPT
OpenClaw
Other self-hosted agents

Open Settings → Connectors → Add custom connector.
Name: Nikiwa
URL: https://pro-api.nikiwa.com/mcp
Click Add, then Connect to open the Nikiwa login and consent screen.

Claude Desktop’s claude_desktop_config.json does not accept remote url servers directly. Use the Connectors UI above.

The plugin above handles this for you. To add the server manually instead:

Open your terminal.

Add the server:

claude mcp add --transport http nikiwa https://pro-api.nikiwa.com/mcp

Add --scope user to make it available in all your projects.

This triggers an OAuth flow to connect Claude Code to your Nikiwa account.
If authentication doesn’t start automatically, run /mcp inside Claude Code, select nikiwa, and choose Authenticate.

Enable Settings → Apps & Connectors → Advanced → Developer mode.
Add a connector with MCP server URL https://pro-api.nikiwa.com/mcp.
Choose OAuth as the authentication method and complete the Nikiwa login.

On the host running your OpenClaw gateway:

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 rather than OAuth. Create one at nikiwa.com under profile → MCP Keys, and pass it as a header:

openclaw mcp set nikiwa '{"url":"https://pro-api.nikiwa.com/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer nkw_live_YOUR_KEY"}}'

NanoClaw, ZeroClaw, and similar self-hosted assistants run headless, so use an API key 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):

{
  "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"
      }
    }
  }
}

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 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.
Browser doesn’t open: your client may not support OAuth for remote MCP servers. Use an API key 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).

​One-command install

​Pick your client

​Verify

​Troubleshooting

One-command install

Pick your client

Verify

Troubleshooting