MCP Router Server

Created By
r2r0garzaa year ago
Overview

what is MCP Router Server?

MCP Router Server is a FastAPI-based server that routes requests to multiple LLM providers (such as OpenAI, LM Studio, OpenRouter, Ollama, Claude, Azure, etc.) through a unified REST API.

how to use MCP Router Server?

To use MCP Router Server, install the dependencies, configure the environment variables, and run the server. You can then test the health check and use the /ask endpoint to interact with the LLM providers.

key features of MCP Router Server?

  • Switch between LLM providers by editing the .env file.
  • Context-aware chat requests via the /ask endpoint.
  • Health check endpoint at /health.
  • Provider abstraction for various LLMs.
  • Easy deployment and configuration.

use cases of MCP Router Server?

  1. Integrating multiple LLM providers into a single application.
  2. Creating a chat application that can switch between different AI models.
  3. Testing and comparing responses from various LLMs.

FAQ from MCP Router Server?

  • What LLM providers are supported?

The server supports OpenAI, LM Studio, OpenRouter, Ollama, Claude, and Azure Foundry AI.

  • Is there a health check feature?

Yes, you can check the health of the server using the /health endpoint.

  • How do I switch LLM providers?

You can switch providers by editing the .env file to set your desired provider keys and options.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
r2r0garza
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago