OpenRouter Web Search MCP Server

Created By
ChristianScha year ago
An MCP server providing websearch using openrouter :online
Overview

What is OpenRouter Web Search MCP?

OpenRouter Web Search MCP is an MCP server that provides a web search tool using OpenRouter's online models to generate concise and up-to-date answers to search queries.

How to use OpenRouter Web Search MCP?

To use the server, install it using Go, set up the required environment variables including your OpenRouter API key, and run the server with the appropriate command.

Key features of OpenRouter Web Search MCP?

  • Exposes an MCP-compatible server over stdio.
  • Provides a search_web tool that accepts search queries and returns fact-based answers as plain text.

Use cases of OpenRouter Web Search MCP?

  1. Performing quick web searches for information retrieval.
  2. Integrating with applications that require real-time search capabilities.
  3. Enhancing chatbots with web search functionalities.

FAQ from OpenRouter Web Search MCP?

  • What programming language is used for this project?

The project is implemented in Go.

  • Do I need an API key to use the server?

Yes, an OpenRouter API key is required to access the web search functionality.

  • Is there a default model name provided?

Yes, the default model name is google/gemini-2.5-pro-exp-03-25:free:online, but it can be customized.

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

9 hours ago