Skip to main content
Nito ships an MCP server inside the command line tool. It proxies the hosted Nito tools over stdio, so any Model Context Protocol host, Claude Desktop, Cursor, or your own agent, can call Nito the way the plugin does. There is no separate package to install: the server is nito agent mcp serve.
Most users never need this. The plugin already connects to Nito for /nito: and $nito: commands. Reach for the MCP server when you want a different host, or your own agent, to call the same Nito tools directly. Optional at launch.

​
Quick Start

1

Install and sign in

Install the command line tool (see Install in Claude Code), then sign in once. Nito authenticates through nito agent login and stores a credential in your OS keychain, so no key or token goes into your host config.
2

Add Nito to your MCP host config

Drop this into your host’s MCP config file:
Common config paths:
3

Restart your MCP host

Your agent now has the Nito tools available. Try asking it to list Nito-supported models or run a completion.

​
The Tools

The server exposes exactly these tools, each with the nito. prefix. The set is fixed: no undocumented tools are exposed, and a missing required tool is reported rather than hidden.
  • nito.auth_status confirms who you are connected as and when the connection expires. It returns metadata only, never the credential itself.
  • nito.account_status returns your plan and usage. The compact projection returns just the rendered status-card fields, including the eligible-Free monthly plugin-request limit, the remaining count, and the UTC reset, and omits identifiers, scopes, and token metadata.
  • nito.models_list lists the catalog. Plain {} returns the full compatible list; projection=picker returns only id, display_name, and privacy_tier, plus next_cursor, total, and catalog_revision for paging.
  • nito.chat_complete is a single, non-streaming completion. It applies the same model policy as the rest of Nito, so premium and privacy rules are enforced here too.
  • nito.chat_fusion runs a multi-model Fusion and returns each participant plus the synthesis, along with safe attestation fields. It is available over OAuth sign-in.
privacy_tier is the API’s name for the model’s privacy level. These docs say level; the field kept the older word.

​
Privacy and Limits Still Apply

The MCP server is a different transport, not a different set of rules. The privacy level still follows the model, premium and beta model policy is enforced on nito.chat_complete, and rate limits are returned as normal tool errors with canonical rate_limited codes when you go over. Prompts, tool arguments, and completions are never persisted or logged server-side; any conversation history lives on your machine.

​
Running the Server

Your MCP host normally launches nito agent mcp serve for you from the config above, but you can run it directly to test it or to pass flags:

​
Options

nito agent mcp serve accepts a couple of flags for advanced setups: To pin a profile in your host config instead:
If your host reports the server as disconnected, check that nito agent status shows you signed in, and that nito is on the PATH your MCP host runs with. Hosts launched from the GUI sometimes have a different PATH than your shell.

​
How This Differs From the Plugin

The Claude Code and Codex plugin already connect to Nito for you, so you do not need this to use /nito: or $nito: commands. Reach for nito agent mcp serve when you want a different MCP host, or your own agent, to call the same Nito tools directly.

Nito CLI

Install, the command index, and the terminal front door.

Choosing a Model

Which models the tools can reach, and their privacy levels.