search-fetch-server MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is search-fetch-server MCP Server?

The search-fetch-server MCP Server is a TypeScript-based Model Context Protocol server that implements a simple notes system, demonstrating core MCP concepts through resources representing text notes, tools for creating and fetching notes, and prompts for generating summaries.

how to use search-fetch-server MCP Server?

To use the server, install the dependencies, build the server, and configure it with Claude Desktop. You can create notes, fetch content from URLs, and perform searches using the provided tools.

key features of search-fetch-server MCP Server?

  • Resources for managing text notes with URIs and metadata.
  • Tools for creating new notes, fetching URLs, and performing DuckDuckGo searches.
  • Prompts for generating summaries of stored notes.

use cases of search-fetch-server MCP Server?

  1. Creating and managing a personal notes system.
  2. Fetching and converting web content into markdown format.
  3. Performing searches to gather information from the web.

FAQ from search-fetch-server MCP Server?

  • What is the purpose of the search-fetch-server?

It serves as a notes management system that allows users to create, fetch, and summarize notes using a Model Context Protocol.

  • How do I install the server?

You can install it by running npm install and then build it using npm run build.

  • Can I use this server on different operating systems?

Yes! The server can be configured to work on both MacOS and Windows.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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)

10 hours ago