Wikipedia MCP Image Crawler

Created By
dazeba year ago
A Wikipedia Image Search Tool. Follows Creative Commons Licences for images and uses them in your projects via Claude Desktop/Cline.
Overview

What is Wikipedia MCP Image Crawler?

Wikipedia MCP Image Crawler is a tool designed to search and retrieve images from Wikipedia Commons, ensuring compliance with Creative Commons licenses for use in various projects.

How to use Wikipedia MCP Image Crawler?

To use the crawler, install it locally by cloning the repository, installing dependencies, and configuring it with the Claude Desktop App or VSCode extensions. Once set up, you can search for images or fetch detailed metadata using the provided tools.

Key features of Wikipedia MCP Image Crawler?

  • wiki_image_search: Search for images on Wikipedia Commons with customizable result limits.
  • wiki_image_info: Retrieve detailed information about specific images, including license and author details.

Use cases of Wikipedia MCP Image Crawler?

  1. Finding images for academic projects while ensuring proper attribution.
  2. Retrieving public domain images for creative works.
  3. Integrating image search capabilities into applications using the MCP server.

FAQ from Wikipedia MCP Image Crawler?

  • Can I use images found through this tool for commercial purposes?

Yes, as long as the images are in the public domain or have appropriate licenses.

  • What are the prerequisites for installation?

You need Node.js 18 or higher and a package manager like npm or pnpm.

  • How do I get detailed information about an image?

Use the wiki_image_info tool with the title of the image to fetch its metadata.

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

a day ago