> ## 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.

# MCP Server

> Connect Claude, ChatGPT, or any MCP client to Nikiwa's blockchain intelligence tools.

Nikiwa runs a Model Context Protocol (MCP) server that exposes its blockchain wallet, token, transaction, and prediction-market tools to any MCP-compatible client, including Claude, ChatGPT, and your own agents. Once connected, your assistant can query on-chain data directly and reason over the results.

## Server details

<CardGroup cols={2}>
  <Card title="Endpoint" icon="link">
    `https://pro-api.nikiwa.com/mcp`
  </Card>

  <Card title="Transport" icon="satellite-dish">
    Streamable HTTP
  </Card>

  <Card title="Server name" icon="tag">
    `nikiwa-tools`
  </Card>

  <Card title="Auth" icon="lock">
    OAuth or Bearer [API key](/mcp/api-keys)
  </Card>
</CardGroup>

## What the server exposes

Nikiwa exposes blockchain data as deterministic tools. As the server describes itself to clients:

> Nikiwa exposes blockchain wallet, token, transaction, and prediction-market data as deterministic tools. It does NOT route, interpret, or synthesize. Each tool returns structured data and YOU compose and reason over the results.

Alongside tools, the server provides:

* **Resources**, including `nikiwa://chains` (the valid network list) and `nikiwa://usage` (composition recipes), which clients can read to ground their calls.
* **Prompts**, ready-made composition recipes for common multi-tool questions.

See the full [tool catalog](/mcp/tools).

<Info>
  The MCP server exposes the full tool set. The public [Tools API](/api-reference/overview) exposes only a curated subset.
</Info>

## Two ways to authenticate

<CardGroup cols={2}>
  <Card title="OAuth (recommended)" icon="user-shield" href="/mcp/connect-oauth">
    Best for interactive clients such as Claude and ChatGPT. Sign in and approve a consent screen. There is no key to copy or store.
  </Card>

  <Card title="API key" icon="key" href="/mcp/api-keys">
    Best for scripts and self-hosted agents. Pass a developer key as a Bearer token.
  </Card>
</CardGroup>

## Using tools well

* **Provide exact entities**: a wallet, token, or contract address, a transaction hash, and a network. Tools are deterministic and do not guess.
* **Resolve first**: if you only have a symbol, call `resolve_token_symbol`; for an ENS name, call `resolve_ens`.
* **Read `nikiwa://chains`** for the valid network list rather than hard-coding it.
* Each tool returns its data object, `{status: no_data}`, or `{status: error}`.