INDIVIDUAL MCP TOOL

compare_hardware

Use this when the user compares two to four machines.

llmconfigurator.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp

No auth detected

Connect to this endpoint to inspect the live schema for compare_hardware and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

llmconfigurator.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.llmconfigurator]
url = "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "llmconfigurator": {
      "type": "http",
      "url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: llmconfigurator
Remote MCP URL: https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "llmconfigurator": {
      "url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "llmconfigurator": {
      "type": "http",
      "url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "llmconfigurator",
  "transport": "streamable-http",
  "url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

search_catalog — Use this first when the user names a GPU, Mac, mini PC or language model and you need its id for the other tools.
check_hardware_fit — Use this when the user asks whether one specific model runs on one specific machine, at what memory cost, and roughly how fast.
models_for_hardware — Use this when the user asks what models a given machine can run.
get_model_specs — Use this when the user asks about one model's size, architecture, context window or licence.