Version 2.0 is here

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Mixelpixx Google Search MCP Server?

Mixelpixx Google Search MCP Server is an MCP (Model Context Protocol) server that provides Google search capabilities and webpage content analysis tools, enabling AI models to perform Google searches and analyze webpage content programmatically.

How to use Mixelpixx Google Search MCP Server?

To use the server, clone the repository, install the necessary Node.js dependencies, configure your Google API credentials, and start the server. You can then utilize various tools for searching and extracting webpage content.

Key features of Mixelpixx Google Search MCP Server?

  • Google Custom Search integration
  • Advanced search features (filters, sorting, pagination, categorization)
  • Webpage content analysis in multiple formats (markdown, HTML, plain text)
  • Batch webpage analysis
  • Result categorization and classification
  • Content summarization
  • Optimized, human-readable responses
  • MCP-compliant interface

Use cases of Mixelpixx Google Search MCP Server?

  1. Performing automated Google searches for data retrieval.
  2. Analyzing and summarizing webpage content for research purposes.
  3. Extracting information from multiple sources for comparative analysis.

FAQ from Mixelpixx Google Search MCP Server?

  • What are the prerequisites for using the server?

You need Node.js (v16 or higher), a Google Cloud Platform account, a Custom Search Engine ID, and a Google API Key.

  • Is there a built version available for distribution?

Yes, you can build the TypeScript code and create a distribution package with only the necessary files.

  • How does the server handle errors?

The server provides detailed error messages for missing or invalid API credentials, failed search requests, invalid webpage URLs, and network connectivity issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
Activity

Recommend Servers

View All
Crevio

a day ago
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)

18 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago