External MCP Server

Multi-LLM MCP server for Claude Code & Codex — route AI agent work across 20+ low-cost provider buckets with round-robin dispatch and quota-aware

Local serverstdioGo

What is the External MCP server?

Connect External to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Multi-LLM MCP server for Claude Code & Codex — route AI agent work across 20+ low-cost provider buckets with round-robin dispatch and quota-aware fallback. The external mcp server is what makes that connection.

What the server does

Your Google + Groq + OpenRouter + Ollama Cloud free tiers, plus cheap direct APIs like DeepSeek, all have separate provider buckets. external-agents treats them as one pool: round-robin dispatch, cooldown-aware, auto-fallback on 429. Same agentic workload that used to cost $10-100/day on one premium model can often run at effectively $0-very-low-cost. Also the perfect substrate for LLM-Council-style multi-model panels — pick_agents gives you N distinct-provider picks in one call.

external-agents is one piece of Mrrlin — an AI orchestration platform for solo developers and small teams. If you like this package, you'll probably like the rest of Mrrlin.

Installation

@mrrlin-dev/external-agents on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Multi — step debugging with unclear root cause
  • Codexcursor-agent
  • kiro-cli — The kiro-cli tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: GROQ_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. External's toolset — Multi, Codex, kiro-cli — is a fair guide to whether it matches your workflow. It is maintained by aiuxsolutions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
Multistep debugging with unclear root cause
Codex**cursor-agent**
kiro-cliThe kiro-cli tool exposed by this server.

How to install the External MCP server

{
  "mcpServers": {
    "external-agents": {
      "command": "npx",
      "args": ["-y", "@mrrlin-dev/external-agents"],
      "env": {
        "GROQ_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GROQ_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use External to Multi.
  • Use External to Codex.
  • Use External to kiro-cli.

Frequently asked questions

It connects External to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Multi, Codex, kiro-cli) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with External directly.