Genpark Multi Llm Router Cost Latency Optimizer Skill

FreeNot checked

Dynamic LLM router for complexity, latency & token cost optimization

by alphaparkinc

GitHub Embed

About

Dynamic LLM router for complexity, latency & token cost optimization

README

GenPark AI Agent Skill -- Dynamic LLM router for complexity, latency & token cost optimization

Quick Start

python example_usage.py

from github.com/alphaparkinc/genpark-multi-llm-router-cost-latency-optimizer-skill

Installing Genpark Multi Llm Router Cost Latency Optimizer Skill

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/alphaparkinc/genpark-multi-llm-router-cost-latency-optimizer-skill

FAQ

Is Genpark Multi Llm Router Cost Latency Optimizer Skill MCP free?

Yes, Genpark Multi Llm Router Cost Latency Optimizer Skill MCP is free — one-click install via Unyly at no cost.

Does Genpark Multi Llm Router Cost Latency Optimizer Skill need an API key?

No, Genpark Multi Llm Router Cost Latency Optimizer Skill runs without API keys or environment variables.

Is Genpark Multi Llm Router Cost Latency Optimizer Skill hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install Genpark Multi Llm Router Cost Latency Optimizer Skill in Claude Desktop, Claude Code or Cursor?

Open Genpark Multi Llm Router Cost Latency Optimizer Skill on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Fetch

Web content fetching and conversion for efficient LLM usage.

by Community

AWS KB Retrieval

Retrieval from AWS Knowledge Base using Bedrock Agent Runtime.

by modelcontextprotocol

Spring AI MCP Server

Provides auto-configuration for setting up an MCP server in Spring Boot applications.

by Community

llm-analysis-assistant

A very streamlined mcp client that supports calling and monitoring stdio/sse/streamableHttp, and can also view request responses through the /logs page. It also