OpenRouter Agents MCP Server

Created By
wheattoast11a year ago
MCP Server that orchestrates research with Claude and Perplexity/GPT/Gemini automatically
Overview

What is OpenRouter Agents MCP Server?

OpenRouter Agents MCP Server is a Model Context Protocol (MCP) server that orchestrates research using AI models like Claude and Perplexity/GPT/Gemini, enabling sophisticated research capabilities.

How to use OpenRouter Agents MCP Server?

To use the server, clone the repository, install dependencies, and configure your OpenRouter API key in the .env file. You can then send research queries through the integrated system in tools like Cline in VS Code.

Key features of OpenRouter Agents MCP Server?

  • Multi-agent orchestration for research tasks
  • Adaptive fallback system for model failures
  • Context-aware refinement of research queries
  • Semantic knowledge base for enhanced query results
  • In-memory caching for fast response times

Use cases of OpenRouter Agents MCP Server?

  1. Conducting complex research queries across multiple AI models.
  2. Utilizing adaptive synthesis for tailored research reports.
  3. Integrating with development environments for seamless research capabilities.

FAQ from OpenRouter Agents MCP Server?

  • What is the purpose of the MCP server?

The MCP server orchestrates research tasks using various AI models to provide comprehensive research outputs.

  • Is there a cost associated with using the server?

The server can utilize both high-cost and low-cost models based on user preferences.

  • What are the prerequisites for running the server?

You need Node.js, npm, Git, and an OpenRouter API key to run the server.

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

20 hours ago
Gpt Scrambler

2 days ago