Remote MCP vs Local MCP Servers: Which Should Your Agent Use?

Local MCP: stdio over npx

**What it is:** Run `npx mcp-media-engine` on your machine. Claude Desktop or your agent communicates via stdio.

**Pros:** - No network latency - Runs immediately (credentials in env var) - No external dependency - Simplest setup

**Cons:** - Agent machine must have Node.js - Scales to one machine only - Restarts kill in-flight requests - Not suitable for cloud agents

**Best for:** Local development, Claude Desktop, single-developer teams.

Remote MCP: HTTP Streaming

**What it is:** A hosted MCP server reachable over HTTPS — for MediaEngine that's https://mcp.mcpmediaengine.com/mcp. Agents connect over the network; nothing to install.

**Pros:** - Works anywhere (cloud, edge, multi-machine) - Scales horizontally - Credentials managed server-side - Persistent (no agent restart = no loss) - Ready for production

**Cons:** - Network latency (~100-500ms) - External dependency (must be running) - Extra configuration - Billing per remote instance

**Best for:** Production agents, teams, cloud deployments, scaling workflows.

Configuration Comparison

Local (Claude Desktop)

{
  "mcpServers": {
    "mediaengine": {
      "command": "npx",
      "args": ["-y", "mcp-media-engine"],
      "env": {
        "MEDIAENGINE_API_KEY": "me_live_..."
      }
    }
  }
}

Remote (Production Agent)

{
  "mcpServers": {
    "mediaengine": {
      "url": "https://mcp.mcpmediaengine.com/mcp",
      "args": [],
      "env": {
        "MEDIAENGINE_API_KEY": "me_live_..."
      }
    }
  }
}

Hybrid Approach

Many teams use both: - **Local:** During development and testing - **Remote:** For production agents and multi-user systems

MediaEngine supports both seamlessly — your agent code doesn't change.

When to Switch

Switch to remote MCP when: - You're deploying to production - Multiple agents need the same models - You need guaranteed uptime - Your agent runs in the cloud (Vercel, AWS, Fly.io) - Load exceeds one machine

Cost Comparison

**Local:** Free (uses your machine resources)

**Remote:** ~$7/month per instance on managed cloud, or self-host for free on your own infrastructure

Conclusion

Start local for development, scale to remote for production. MediaEngine's stable wiring means changing servers doesn't require code changes — just update the config.