llm-model-providers MCP Server

Created By
jhsua year ago
mcp server for fetching available llm models
Overview

what is llm-model-providers MCP Server?

The llm-model-providers MCP Server is a server designed to fetch available models from various LLM (Large Language Model) providers, facilitating easy access to different models for developers.

how to use llm-model-providers MCP Server?

To use the MCP Server, install the necessary dependencies, build the server, and configure it with your LLM provider's API keys. You can also set it up for use with Claude Desktop by adding the server configuration to the appropriate JSON file.

key features of llm-model-providers MCP Server?

  • Fetches available models from multiple LLM providers.
  • Supports configuration for different environments (MacOS and Windows).
  • Includes debugging tools via MCP Inspector for easier troubleshooting.

use cases of llm-model-providers MCP Server?

  1. Integrating various LLM models into applications.
  2. Simplifying the process of switching between different LLM providers.
  3. Debugging and monitoring LLM model interactions during development.

FAQ from llm-model-providers MCP Server?

  • What programming language is the MCP Server built with?

The MCP Server is built using JavaScript.

  • How do I install the MCP Server?

You can install it by running pnpm install after cloning the repository.

  • Is there a way to debug the MCP Server?

Yes! You can use the MCP Inspector for debugging, which provides a URL to access debugging tools in your browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jhsu
Star
0
Language
JavaScript
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