Skip to content
Fast install

Install ModelShortlist in a few minutes.

You need Node.js 20+, an Artificial Analysis API key, and an OpenRouter API key. Pick your client below and ModelShortlist will generate the exact config or command for you.

First-class setup is available for Claude Desktop, Hermes Desktop, Cursor, Claude Code, and VS Code / Copilot.

2 API keys
Artificial Analysis + OpenRouter
1 npm package
@agentic.artists/modelshortlist
No ModelShortlist account
Keys stay local to your MCP process
Install configurator

Pick your client. Copy one thing.

Your keys are used only in this browser tab to generate the config below. They are never submitted to ModelShortlist.

Browser-only
1. Choose your client
2. Paste your upstream keys
3. Copy and install

Claude Desktop → Settings → Developer → Edit Config, then add this server to claude_desktop_config.json

{
  "mcpServers": {
    "modelshortlist": {
      "command": "npx",
      "args": [
        "-y",
        "@agentic.artists/modelshortlist"
      ],
      "env": {
        "ARTIFICIAL_ANALYSIS_API_KEY": "YOUR_ARTIFICIAL_ANALYSIS_KEY",
        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_KEY"
      }
    }
  }
}
After installation, restart or refresh your client if needed. You should see three tools: recommend_models, compare_models, and modelshortlist_status.

Before you install

Get the two upstream keys.

ModelShortlist is BYOK. It does not create, store, or proxy these credentials. Each local MCP process calls the upstream services directly.

Verify it worked

Ask one normal question.

Once your client discovers the three ModelShortlist tools, you do not need special syntax. Just describe the workload and constraints in chat.

“I need the best-value model for a long-running autonomous coding agent. Tool calling is required and I need at least 100k context. Quality matters more than cost, but I care about value.”

Troubleshooting

Windows GUI client cannot find npx: enable the Windows toggle above so the generated config uses npx.cmd. If the app still cannot see Node, use the repository’s guided local setup, which prints absolute executable paths.

Tools do not appear: restart or refresh the MCP client after saving the config, then check that both API keys are present and Node.js 20+ is installed.

Prefer a local clone: run npm run setup after cloning the repo. The setup wizard stores keys in a gitignored local file and prints ready-to-paste configs.