Skip to main content
Glama
ceveyne

find-images-mcp-bridge

by ceveyne

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHAT_WORKING_DIRECTORIESYesAbsolute base directory for all Bionic scratchpads. Example: /Users/ceveyne/.lmstudio/scratchpads
FIND_IMAGES_MCP_INDEXER_URLYesBase URL of the image server. Example: https://127.0.0.1:9760/mcp
FIND_IMAGES_MCP_INDEXER_TOKENYesBearer token for the image server. Example: b2f4b1e2-3g0w-4c8t-3b7q-6n2b5b7x1a9d
FIND_IMAGES_MCP_INDEXER_CA_CERTNoOptional path to the image server's self-signed CA/server certificate; standard certificate validation remains active without this value. Example: /Users/ceveyne/.find-images/server/server.crt

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_imageB

Find visually similar and metadata-related images. Use this tool for cross-modal retrieval over images from several sources across the local network.

tag_imageB

Manage persistent tags for indexed images through the configured image server.

Examples:

  • { "action": "add_tag", "target": "p1", "tags": ["favorite"] }

  • { "action": "remove_tag", "target": ["p1", "v2", "/absolute/path/image.png"], "tags": ["favorite", "reviewed"] }

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

find_image handles retrieval, tag_image handles tag management—two clearly distinct purposes with no overlap. Even though tag_image uses sub-actions, the tool boundary against find_image is unambiguous.

Naming Consistency5/5

Both tools follow a clean verb_noun snake_case pattern (find_image, tag_image). Fully consistent.

Tool Count3/5

Two tools is thin for an image bridge that claims cross-modal retrieval and tag management. It's borderline; the surface earns its place but feels minimal.

Completeness2/5

Only find and tag operations exist. Missing obvious lifecycle operations like indexing new images, listing indexed images, retrieving image metadata/details, or listing/querying existing tags—significant gaps for a retrieval bridge.

Maintenance

ActivityMaintained
ResponsivenessNo issues