mcpField
I
inferenceindexer-mcp

inferenceindexer-mcp

Remote
github.com/DesMartin01AI & Agents0Updated 1w ago
Repository

About inferenceindexer-mcp

inferenceindexer-mcp exposes InferenceIndexer live and historical inference pricing to AI agents and MCP clients for model and provider comparisons. Alongside price lookup, it offers model recommendations and SIT index data.

Key features

  1. 01Recommend models under constraints
  2. 02Retrieve model prices, trends, and endpoints
  3. 03Search and inspect model details
  4. 04Compare model prices across providers
  5. 05Browse providers and pricing statistics
  6. 06Query SIT Composite index and history

Use cases

  1. 01Filter models by budget and quality needs
  2. 02Review a model's historical price changes
  3. 03Compare providers for the same model
  4. 04Track inference price index trends

MCP support

The MCP server gives clients tools for InferenceIndexer model pricing, historical data, provider comparisons, and the SIT index. It can run locally over stdio or connect remotely through Streamable HTTP.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.inferenceindexer.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
pypiinferenceindexer-mcp0.1.1

Tools

10
ParameterTypeRequiredDescription
zdrbooleanNo
limitintegerNo
modalitystringNo
reasoninganyNo
context_minanyNo
eu_sovereignbooleanNo
budget_max_usd_per_manyNo

Details

From the project README

InferenceIndexer MCP Server

Model Context Protocol server exposing InferenceIndexer's live + historical inference pricing as agent callable tools. Instead of an agent assembling inference pricing itself (slow, incomplete), it can call these tools to get complete pricing, historical trends, provider comparison, and the SIT index.

Tools

ToolDescription
recommend_modelsCall this first: rank models under your constraints (budget, context, ZDR, quality floor) with ready-to-call endpoint configs
explain_modelEverything about one model in one call: pricing, trend, endpoints, privacy flags
search_modelsSearch/list models with current pricing (by text, tier, sort)
get_modelFull detail + current price for one model
get_model_historyHistorical price trends for one model (the differentiator)
list_providersAll providers with model counts + price stats
get_providerDetail for one provider (models, tiers, price range)
get_composite_latestCurrent SIT-Composite index value + tier breakdown
get_composite_historySIT-Composite index history / trend
compare_providersPrice of one model across all providers that host it

Config (env)

  • II_API_BASE - InferenceIndexer API base (default https://api.inferenceindexer.ai)
  • II_API_KEY - Optional bearer key (public server works without one; a key raises rate limits)
  • II_SSR_SECRET - Optional first-party secret for self-hosted/higher-tier use only. Not set on the public server.

Run

stdio (recommended for local/agent-run):

uv sync
uv run inferenceindexer-mcp

Serve over HTTP/SSE (for remote clients, e.g. the hosted endpoint at https://api.inferenceindexer.ai/mcp):

uv run inferenceindexer-mcp --transport streamable-http --port 8899

Connect an agent / MCP client

Claude Desktop / generic MCP client (stdio):

{
  "mcpServers": {
    "inferenceindexer": {
      "command": "uvx",
      "args": ["inferenceindexer-mcp", "--transport", "stdio"]
    }
  }
}

Updated Oct 2026. Hosted (no install): https://api.inferenceindexer.ai/mcp - add "url": "https://api.inferenceindexer.ai/mcp" to mcpServers for streamable-http clients.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.