Pic Nicked MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Google API key for custom search | |
| SEARCH_ENGINE_ID | Yes | Google search engine ID |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_imageC | Search the image(s) online |
| persist_imageA | Store image at URL to folder relative to current workspace. If targetPath does not exist, the tool will create it automatically. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
search_image and persist_image have completely distinct purposes: one looks up images online, the other saves a specific image locally. There is no overlap or ambiguity between them.
Both tools follow the exact same verb_noun pattern with snake_case (search_image, persist_image), making the naming predictable and consistent.
With only 2 tools, the server feels minimal and is on the thin side. The count is acceptable if the scope is strictly search-and-save, but it is borderline for a utility server.
The core operations (search and persist) are covered, but there is no way to list, delete, or otherwise manage persisted images. This is a notable gap in the image lifecycle, making the surface feel incomplete.