Since v0.1.238, Nio answers MCP at https://nioai.run/mcp. Any client that can add a remote MCP server can use it. On your own computer, Claude Code, Codex CLI, Cursor and VS Code can keep using the local server: nio mcp install --client <claude|codex|cursor|vscode>.
| What the client can do | Tools | Needs |
|---|---|---|
| Use your Nio memory | memory_search, memory_save, task_list, project_context, auth_whoami |
A Nio API key or an OAuth sign-in |
| Hand Nio project tasks | nio_ask, nio_task_status, nio_task_cancel, project_status, project_decisions, project_record, project_resume |
A Nio API key, and nio connect running on your computer |
Your code never runs on nioai.run. Project tasks travel to your own Nio, which runs them with your permission settings. Nio changes files in a project only after you allow it for that project. Allow it on your computer with nio cli allow-project <your account> <project folder>.
You need a Nio API key for your account, or OAuth sign-in where the client supports it.
OpenAI Responses API
{ "type": "mcp", "server_label": "nio", "server_url": "https://nioai.run/mcp", "authorization": "<NIO_API_KEY>" }
Send authorization on every request; OpenAI does not store it.
Claude API (MCP connector)
"mcp_servers": [{ "type": "url", "url": "https://nioai.run/mcp", "name": "nio", "authorization_token": "<NIO_API_KEY>" }],
"tools": [{ "type": "mcp_toolset", "mcp_server_name": "nio" }]
Claude.ai: Customize > Connectors > Add custom connector, URL https://nioai.run/mcp. You can choose either kind of sign-in:
Authorization: Bearer <NIO_API_KEY>. This also gives project tools.ChatGPT: add a custom connector (developer mode) with URL https://nioai.run/mcp and authentication OAuth. Sign in with your nioai.run email and password (plus your authenticator code if MFA is on) and allow the memory scope. ChatGPT cannot send API keys, so it gets the memory tools. Which ChatGPT plans can add custom connectors is up to OpenAI.
Your account lists the apps you signed in to and can disconnect them (GET and DELETE /auth/oauth/grants).
nio connect: project tasks on your computernio connect
Run it in a project folder, or name the folders: nio connect --project D:\work\shop --project blog=D:\work\site. Each project is offered under its folder name, or the name before =. The gateway learns names only, never paths.
NIO_API_KEY when set, otherwise your nio cli auth-login.--name <name> (default: the host name). A second nio connect with the same name takes over from the first. An account can connect up to 5 computers.--websocket or --polling forces one). It pings every 30 s and reconnects by itself, backing off up to 60 s.Then, from the client, project_context lists your connected projects. nio_ask with {"project": "shop", "prompt": "..."} returns a task_id at once, and nio_task_status returns the result. If no computer is connected, project tools answer “Start Nio on your computer with nio connect, then try again.”