Skip to main content
Glama
dazeb

wikipedia-mcp-image-crawler

by dazeb

Wikipedia MCP Image Crawler

A Model Context Protocol (MCP) server for searching and retrieving images from Wikipedia Commons. This server provides tools to search for images and fetch detailed metadata through the Wikipedia API.

I created this tool because i needed images of Greek philosopher's. I needed to mak sure i had full attribution and licenses. This will search wikipedia only and download images that are in the public domain and free to use.

Features

Tools

  • wiki_image_search - Search for images on Wikipedia Commons

    • Search by query with customizable result limits (1-50)

    • Returns image URLs, dimensions, MIME types, and sizes

  • wiki_image_info - Get detailed information about specific images

    • Fetches comprehensive metadata including license and author

    • Returns full resolution URLs and description links

Related MCP server: webfetch

Installation

Prerequisites

  • Node.js 18 or higher

  • npm or pnpm package manager

Local Installation

  1. Clone the repository:

    git clone https://github.com/dazeb/wikipedia-mcp-image-crawler.git
    cd wikipedia-mcp-image-crawler
  2. Install dependencies:

    pnpm install
  3. Build the server:

    pnpm run build

Integration with Claude

Claude Desktop App

Add the server configuration to your Claude config file:

MacOS:

nano ~/Library/Application\ Support/Claude/claude_desktop_config.json

Linux:

nano ~/.config/Claude/claude_desktop_config.json

Windows:

notepad %APPDATA%\Claude\claude_desktop_config.json

Add this configuration (adjust the path to where you cloned the repository):

{
  "mcpServers": {
    "wikipedia-mcp-server": {
      "command": "node",
      "args": ["/absolute/path/to/wikipedia-mcp-image-crawler/build/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

VSCode Extensions

Cline VSCode Extension

For the Cline VSCode extension, add to:

MacOS:

~/Library/Application\ Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

Linux:

~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

Windows:

%APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

For VS Code Insiders, replace Code with Code - Insiders in the paths above.

Add this configuration to the JSON file:

{
  "mcpServers": {
    "wikipedia-mcp-server": {
      "command": "node",
      "args": ["/absolute/path/to/wikipedia-mcp-image-crawler/build/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

If the file already contains other MCP servers, add this entry to the existing mcpServers object.

Usage

Once installed, the server provides two main tools:

Search for images matching a query:

{
  "name": "wiki_image_search",
  "arguments": {
    "query": "golden gate bridge",
    "limit": 5
  }
}

Image Information

Get detailed metadata for a specific image:

{
  "name": "wiki_image_info",
  "arguments": {
    "title": "File:Golden Gate Bridge.jpg"
  }
}

Development

Running in Watch Mode

For development with auto-rebuild:

pnpm run watch

Debugging

Since MCP servers communicate over stdio, use the MCP Inspector for debugging:

pnpm run inspector

This will provide a URL to access the debugging interface in your browser.

Available Tools

2 tools
wiki_image_infoB

Get detailed information about a specific Wikipedia image

ParametersJSON Schema
NameRequiredDescriptionDefault
titleYesTitle/filename of the image on Wikipedia Commons

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must compensate, but it only states 'Get detailed information' without any behavioral context (e.g., read-only, permissions, side effects, rate limits). The agent has no additional information beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundancy. Every word serves a purpose, making it highly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having only one parameter and no output schema, the description fails to specify what 'detailed information' includes (e.g., metadata, dimensions, licensing). This inadequacy undermines the tool's usability for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'title' is fully described in the input schema (100% coverage). The tool description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb-resource structure: 'Get detailed information about a specific Wikipedia image'. It directly contrasts with the sibling tool 'wiki_image_search' which likely handles searching, so the purpose is well-defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus the sibling 'wiki_image_search'. The description does not provide any conditions, exclusions, or alternative tool suggestions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedwiki_image_info
    • First observedwiki_image_search

TDQS

B3.2/5.0
Disambiguation5/5

The two tools serve clearly distinct purposes: one searches for images on Commons, the other retrieves details about a specific image. There is no ambiguity or overlap in their functionality.

Naming Consistency5/5

Both tool names follow the consistent pattern 'wiki_image_<verb>', using snake_case and a clear prefix. This makes the tool set easy to navigate and predict.

Tool Count3/5

With only two tools, the server feels minimal for something called an 'image crawler'. While the tools cover basic search and info retrieval, more operations (e.g., download, list) would better justify the name.

Completeness2/5

The tool set lacks critical operations for a crawler, such as downloading images or browsing categories. An agent would hit dead ends when trying to actually collect image data.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    This MCP server enables AI assistants to search for images on Wikimedia Commons, providing detailed metadata and optional thumbnail combinations to assist AI models in visual comparisons.
    1
    2
    Apache 2.0
  • A
    license
    A
    quality
    A
    maintenance
    License-first federated image search for AI agents and humans. Exposes MCP tools for concise, attribution-aware image discovery, license probing, and guarded downloads across open, platform, and editorial sources.
    7
    45
    3
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to access Wikipedia content, search articles, retrieve historical events, and fetch images through the Wikipedia API.
    4
    31
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dazeb/wikipedia-mcp-image-crawler'

If you have feedback or need assistance with the MCP directory API, please join our Discord server