Skip to main content
Glama
XPDevs

XPDevs Image Search

by XPDevs

XPDevs Image Search

An MCP server that lets LM Studio search the web for images and show them in chat.

What it does

  • Searches DuckDuckGo for images (no API key needed)

  • Downloads and resizes images

  • Returns them inline in the LM Studio chat

Related MCP server: searxng-mcp

How to use it

Open LM Studio, go to the Program tab (right sidebar), click Install > Edit mcp.json, and add:

{
  "mcpServers": {
    "XPDevs/image-search": {
      "command": "node",
      "args": ["/full/path/to/image-search-mcp/dist/index.js"]
    }
  }
}

Replace /full/path/to/ with the actual path to the folder.

Save the file. LM Studio will load the server automatically. Start a new chat and you will see search_images appear in the tools list.

Tool parameters

Parameter

What it does

query

What to search for. Keep it descriptive.

count

How many images to return (1-10, default 1).

site

Optional. Restrict to one domain (eg "reddit.com", "unsplash.com").

width

Optional. Output width in pixels. Default 800.

height

Optional. Output height in pixels. Default 800.

System requirements

  • Node.js (LM Studio bundles this, no separate install needed)

  • The folder must stay in place while LM Studio is running

Build from source

cd image-search-mcp
npm install
npm run build

Do this after pulling updates or making changes to the source.

Available Tools

1 tool
search_imagesD
ParametersJSON Schema
NameRequiredDescriptionDefault
siteNoRestrict to a domain
countNoNumber of images (1-10)
queryYesWhat to search for
widthNoOutput width
heightNoOutput height

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

TDQS

D1.8/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or misselection, so disambiguation is perfect.

Naming Consistency5/5

A single tool name follows a clear pattern and there are no inconsistencies to evaluate.

Tool Count3/5

One tool is borderline for an image search server; while a single search tool could suffice, the lack of additional functionality feels thin for a typical use case.

Completeness2/5

The server lacks tool descriptions and has no additional tools for managing or refining searches, leaving significant gaps in the expected functionality.

Maintenance

ActivityStale
ResponsivenessSyncing

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

  • F
    license
    Not graded
    quality
    D
    maintenance
    A lightweight MCP server that enables LLMs to search the web via DuckDuckGo, search GitHub code repositories, and extract clean content from web pages in LLM-friendly formats.
    8
  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that wraps a local SearXNG instance to provide private, customizable web search capabilities. It enables AI assistants to perform queries with support for specific parameters like results limits, language, and time ranges.
    241
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A minimal, production-ready MCP server enabling LLMs to perform web searches via DuckDuckGo without API keys, supporting SSE streaming and LM Studio compatibility.
    1
    BSD 3-Clause

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/XPDevs/LM-Studio-Image-Search'

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