wikipedia-mcp-image-crawler
Allows searching for images on Wikipedia Commons and fetching detailed metadata including license and author information.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@wikipedia-mcp-image-crawlersearch for images of Aristotle"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 CommonsSearch by query with customizable result limits (1-50)
Returns image URLs, dimensions, MIME types, and sizes
wiki_image_info- Get detailed information about specific imagesFetches 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
Clone the repository:
git clone https://github.com/dazeb/wikipedia-mcp-image-crawler.git cd wikipedia-mcp-image-crawlerInstall dependencies:
pnpm installBuild 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.jsonLinux:
nano ~/.config/Claude/claude_desktop_config.jsonWindows:
notepad %APPDATA%\Claude\claude_desktop_config.jsonAdd 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.jsonLinux:
~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonWindows:
%APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.jsonFor 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:
Image Search
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 watchDebugging
Since MCP servers communicate over stdio, use the MCP Inspector for debugging:
pnpm run inspectorThis will provide a URL to access the debugging interface in your browser.
Available Tools
2 toolswiki_image_infoB
Get detailed information about a specific Wikipedia image
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Title/filename of the image on Wikipedia Commons |
TDQS
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.
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.
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.
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.
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.
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.
wiki_image_searchC
Search for images on Wikipedia Commons
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query for images | |
| limit | No | Maximum number of results (1-50) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description lacks details about what the tool returns (e.g., list of URLs, metadata) or any side effects. The description merely restates the tool's name without behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence, which is concise but not front-loaded with the most critical information. It could be more structured to include what the output contains.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description does not mention the output format, which is missing since no output schema is provided. For a search tool, explaining the return type (e.g., image titles and URLs) is important for tool selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both parameters documented in the schema. The description adds no additional meaning beyond what the schema already provides, 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (search) and resource (images on Wikipedia Commons). It is a specific verb+resource pair that differentiates from the sibling tool wiki_image_info, which likely retrieves details for a single image.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus the sibling wiki_image_info. The description does not mention when searching is appropriate or when to use the alternative.
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.
2 tool updates
v0.1.0- First observed
wiki_image_info - First observed
wiki_image_search
TDQS
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.
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.
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.
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
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
Wikimedia Commons file/image/audio/video search via MediaWiki Action API
Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers.
Wikipedia, Wikidata and Wiktionary as clean JSON, not HTML. 1.9M searchable. Free, no auth.
Related MCP Servers
- AlicenseBqualityDmaintenanceThis 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.12Apache 2.0
- AlicenseAqualityAmaintenanceLicense-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.7453MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to access Wikipedia content, search articles, retrieve historical events, and fetch images through the Wikipedia API.4311MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search for images on Wikimedia Commons, returning structured metadata and a composite thumbnail grid for visual comparison.1412MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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