olostep-mcp

Created By
Olostepa year ago
Search Google, scrape webpage and retrieve content in markdown.
Overview

what is Olostep MCP Server?

Olostep MCP Server is a powerful web scraping API that allows users to search the web and scrape content while avoiding bot detection and IP blocking.

how to use Olostep MCP Server?

To use the Olostep MCP Server, install and run it using the command: env OLOSTEP_API_KEY= npx -y olostep-mcp. You can then utilize its various tools to scrape web content.

key features of Olostep MCP Server?

  • Retrieves webpage content in markdown format.
  • Provides a website map sorted by relevance to a search query.
  • Fetches structured data from Google search results using the SERP API.

use cases of Olostep MCP Server?

  1. Extracting content from various websites for data analysis.
  2. Mapping website URLs based on specific search queries.
  3. Gathering structured data from Google search results for research purposes.

FAQ from Olostep MCP Server?

  • Is the Olostep MCP Server free to use?

The documentation does not specify pricing, so check the GitHub page for more details.

  • What programming languages can I use with the Olostep MCP Server?

The server is compatible with all major AI coding assistants, making it versatile for various programming environments.

  • How does the server avoid bot detection?

The server employs techniques to mimic human behavior, thus reducing the chances of detection.

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