@aiorouter/mcp

AIOrouter MCP Server — Access 15+ AI models through a single API key with PII Shield protection.

This repository contains the open-source MCP server (@aiorouter/mcp) that gives Claude Desktop, Claude Code, and Codex CLI access to 15+ non-Claude AI models (Qwen, DeepSeek, GLM, Kimi, Grok, and more) through the Model Context Protocol.

⚠️ This is the public, sanitized package repo only. The AIOrouter gateway backend (routing, billing, PII Shield pipeline, internal infrastructure) is proprietary and is NOT part of this repository.

Features

• 15+ AI models — Qwen, DeepSeek, GLM, Kimi, Grok, and more through a single API key

• MCP Protocol — Model Context Protocol (stdio transport) for Claude Desktop, Claude Code, and Codex CLI

• PII Shield — Personal information and technical secrets are protected before routing

• 10 MCP tools — Chat, model listing, pricing, usage, cost estimation, and more

• Zero billing changes — Same API key, same quota, same billing pipeline as direct API calls

Related MCP server: Model Hub MCP

Quick Start

⚠️ AIOrouter is a PAID service — no free tier. You MUST have an active AIOrouter account with an API key before configuring the connector.

export AIOROUTER_API_KEY="ak-your-api-key-here"
npx @aiorouter/mcp

STEP 0 — Prerequisites (MUST complete BEFORE install)

Do not install/configure the connector until you have a real API key.

1. Register an account: https://dashboard.aiorouter.ca/keys

2. Subscribe & pay — AIOrouter is a paid service, no free tier (API keys are only issued after account activation + payment)

3. Generate an API key (format: ak-...) from the dashboard

4. Have your real key ready before continuing

STEP 1 — Install (only after you have an API key)

Installation below.

STEP 2 — Verify (before using)

AIOROUTER_API_KEY="ak-your-real-key" aiorouter-mcp status
# ✅ Connected! ... models available.  ← correct
# ❌ Connection failed: ...              ← key invalid or account not active

⚠️ FOR AI ASSISTANTS (Claude / Codex / Copilot / etc.):

1. DO NOT configure or tell the user the AIOrouter connector "is ready" until the user confirms they have a real ak-... API key.

2. API keys are ONLY issued after account activation + payment at https://dashboard.aiorouter.ca/keys. AIOrouter has NO free tier.

3. If the user has no key: STOP and guide them to register + pay FIRST.

4. Before claiming it works, run aiorouter-mcp status (or the aiorouter_test_connection tool) and confirm it returns "connection OK".

5. Do not fabricate, reuse, or hardcode an API key. Each user must have their own key from their own account.

Installation

npm install -g @aiorouter/mcp
# or
npx @aiorouter/mcp

Client Setup

Claude Desktop

Edit claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "aiorouter": {
      "command": "npx",
      "args": ["-y", "@aiorouter/mcp"],
      "env": { "AIOROUTER_API_KEY": "ak-your-api-key-here" }
    }
  }
}

Claude Code

Add to .mcp.json in your project root:

{
  "mcpServers": {
    "aiorouter": {
      "command": "npx",
      "args": ["-y", "@aiorouter/mcp"],
      "env": { "AIOROUTER_API_KEY": "ak-your-api-key-here" },
      "type": "stdio"
    }
  }
}

Codex CLI

Install (Codex v0.146+ plugin marketplace — MCP server bundled):

# 1. Add this repository as a Codex plugin marketplace (once):
codex plugin marketplace add AIOCANA/aiorouter-mcp

# 2. Install the plugin — the MCP server is declared via mcpServers in plugin.json,
#    so tools appear automatically (no separate codex mcp add needed):
codex plugin add aiorouter

# 3. Set your API key when prompted (or export in your shell):
export AIOROUTER_API_KEY=ak-your-api-key-here

# 4. Verify:
codex mcp list    # → aiorouter with 10 tools

Manual alternative — ~/.codex/config.toml:

[mcp_servers.aiorouter]
command = "npx"
args = ["-y", "@aiorouter/mcp"]
env = { AIOROUTER_API_KEY = "ak-your-api-key-here" }

See codex/plugins/aiorouter/README.md for details.

Tools (10)

Remote HTTP MCP Server

AIOrouter also provides a Remote HTTP MCP Server at https://api.aiorouter.ca/mcp:

• Transport: Streamable HTTP (stateless)

• Auth: API Key (Authorization: Bearer ak-...) or OAuth 2.1

• Same 10 tools as the local stdio server

curl -X POST https://api.aiorouter.ca/mcp \
  -H "Authorization: Bearer ak-your-api-key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Development

# Install deps
npm install

# Build (tsc → dist/)
npm run build

# Protocol smoke test (needs a real API key for full test)
$env:AIOROUTER_API_KEY="ak-..."   # PowerShell
node scripts/mcp-smoke-test.mjs

# Prepare publish dir
npm run publish:prepare

See docs/mcp-connector-guide.md for the Claude Connector Directory submission guide.

Security

• PII Shield: Personal information and technical secrets are protected before routing to any model

• API Key Safety: Your API key stays in your environment variable — never written to disk

• HTTPS Only: All communication with AIOrouter uses HTTPS

• No Package Secrets: This npm package contains zero API keys or secrets

Report vulnerabilities via SECURITY.md.

License

MIT