LLM Wrapper MCP Server

Created By
matdev83a year ago
Allow any MCP-capable LLM agent to communicate with or delegate tasks to any other LLM available through the OpenRouter.ai API.
Overview

what is LLM Wrapper MCP Server?

LLM Wrapper MCP Server is a server wrapper that allows any Model Context Protocol (MCP)-capable Large Language Model (LLM) agent to communicate with or delegate tasks to other LLMs available through the OpenRouter.ai API.

how to use LLM Wrapper MCP Server?

To use the LLM Wrapper MCP Server, install it via pip, configure your environment with the OpenRouter API key, and run the server using command-line options to specify the model and other parameters.

key features of LLM Wrapper MCP Server?

  • Implements the MCP specification for standardized LLM interactions.
  • Provides an STDIO-based server for handling LLM requests and responses.
  • Supports tool calls and results through the MCP protocol.
  • Configurable to use various LLM providers via API base URL and model parameters.
  • Integrates with llm-accounting for logging and auditing functionalities.

use cases of LLM Wrapper MCP Server?

  1. Integrating LLM capabilities into applications.
  2. Facilitating communication between different LLMs.
  3. Monitoring and auditing LLM usage and costs.

FAQ from LLM Wrapper MCP Server?

  • How do I install the LLM Wrapper MCP Server?

You can install it using pip: pip install llm-wrapper-mcp-server.

  • What is the default configuration for the server?

The server is configured to use OpenRouter by default, and you can specify the model and API base URL via command-line arguments.

  • Can I use my own LLM models?

Yes! The server is designed to be extensible and can be configured to use various LLM providers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
matdev83
Star
1
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)

2 days ago