Skip to main content
Glama
enesjakozh
husniadil

MCP Image Placeholder Server

by husniadil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

MCP 이미지 플레이스홀더 서버

이는 다양한 공급자로부터 플레이스홀더 이미지를 생성하는 도구를 제공하는 MCP(Model Context Protocol) 서버입니다.

특징

  • 지원되는 공급자로부터 플레이스홀더 이미지를 생성합니다.

  • 두 가지 이미지 공급자를 지원합니다.

    • placehold : 간단한 플레이스홀더 이미지를 제공합니다

    • lorem-picsum : 실제 이미지를 자리 표시자 이미지로 제공합니다.

  • 입력 매개변수를 검증합니다

  • 즉시 사용할 수 있는 이미지 URL을 반환합니다.

Related MCP server: Grok AI Image Generation MCP Server

요구 사항

  • 파이썬 3.9 이상

  • uv 패키지 관리자

설치

  1. 이 저장소를 복제하세요

  2. MCP 서버 구성을 설정합니다.

용법

서버는 하나의 도구를 공개합니다.

image_placeholder

지정된 매개변수를 기반으로 플레이스홀더 이미지 URL을 생성합니다.

매개변수:

  • provider : 사용할 이미지 제공자( placehold 또는 lorem-picsum )

  • width : 이미지의 너비(1-10000)

  • height : 이미지의 높이(1-10000)

보고:

  • 생성된 이미지의 URL 문자열

사용 예:

지엑스피1

구성

이 서버를 데스크톱용 Claude에 연결하려면:

  1. claude_desktop_config.json 에 다음을 추가하세요.

    {
    "mcpServers": {
        "image-placeholder": {
            "command": "uv",
            "args": [
                "--directory",
                "/ABSOLUTE/PATH/TO/PROJECT",
                "run",
                "main.py"
            ]
        }
    }
}

  2. 데스크톱용 Claude 재시작

이 서버를 Cursor에 연결하려면:

  1. 커서 설정 열기

  2. Features 섹션으로 이동하세요

  3. MCP Servers 섹션까지 아래로 스크롤하세요.

  4. Add new MCP server 버튼을 클릭하세요

  5. 다음 정보를 입력하세요:

    • 이름: image-placeholder

    • 유형: command

    • 서버 URL: uv --directory /ABSOLUTE/PATH/TO/PROJECT run main.py

  6. Add ↵ 버튼을 클릭하세요

문제 해결

도구가 감지되지 않으면 uv 명령의 절대 경로를 사용합니다. 예:

/ABSOLUTE/PATH/TO/uv --directory /ABSOLUTE/PATH/TO/PROJECT run main.py

예제 사용 및 출력(커서)

즉각적인:

Create a new directory named "example" and a file named output.html.

Then create a single modern looking page using tailwindcss: https://unpkg.com/@tailwindcss/browser@4

Show a nice header, content, and footer, showing a photo gallery.

Save this into output.html

커서 에이전트의 스크린샷

출력: 예제 출력(커서)

특허

MIT 라이센스

Available Tools

1 tool
image_placeholderA
Generate a placeholder image based on a provider, width, and height.
Use this tool to generate a placeholder image for testing or development purposes.

Args:
    provider: The provider to use for the image, must be either `placehold` or `lorem-picsum`.
    width: The width of the image, must be a positive integer between 1 and 10000.
    height: The height of the image, must be a positive integer between 1 and 10000.
ParametersJSON Schema
NameRequiredDescriptionDefault
providerYes
widthYes
heightYes

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool generates an image but lacks details on behavioral traits like output format (e.g., URL, binary data), error handling, rate limits, or authentication needs. This leaves gaps for an agent to understand how to use it effectively.

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

Conciseness4/5

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

The description is appropriately sized and front-loaded, with the purpose stated first and parameter details organized in a clear 'Args' section. It avoids unnecessary fluff, though the second sentence slightly repeats the purpose without adding new value.

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

Completeness3/5

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

Given no annotations and no output schema, the description is incomplete for a tool that generates output. It explains parameters well but omits details on what the tool returns (e.g., image URL or data), which is critical for an agent to use it correctly. This gap reduces completeness despite good parameter coverage.

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

Parameters5/5

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

The schema description coverage is 0%, but the description compensates fully by explaining all three parameters in the 'Args' section: provider options, width/height ranges, and constraints. This adds crucial meaning beyond the bare schema, making parameters clear and actionable.

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 clearly states the specific action ('Generate a placeholder image') and resource ('based on a provider, width, and height'), with the second sentence reinforcing the purpose for testing/development. It uses precise verbs and distinguishes the tool's function without tautology.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool ('for testing or development purposes'), which helps guide the agent. However, since there are no sibling tools mentioned, it cannot differentiate from alternatives, though this is not a flaw given the context.

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.

  1. 1 tool update
    • First observedimage_placeholder
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool name 'image_placeholder' follows a clear and consistent verb_noun pattern. Since there is only one tool, naming consistency is inherently perfect.

Tool Count2/5

A single tool for an image placeholder server feels thin and limited in scope. While it serves a specific purpose, it lacks related operations like listing available providers or generating images with additional parameters, making it borderline too few for practical use.

Completeness3/5

The tool covers the core functionality of generating placeholder images with basic parameters. However, there are notable gaps, such as no tools for retrieving image metadata, managing providers, or handling errors beyond parameter validation, which limits the server's utility.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

  • Cloudinary MCP Server

    felores
    A
    license
    B
    quality
    D
    maintenance
    This server provides tools for uploading images and videos directly to Cloudinary using Claude/Cline, facilitating resource management with customizable options like resource type and public ID.
    1
    14 npm
    10
    MIT

  • Lorem Ipsum MCP Server

    ssv445
    F
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol server that enables image generation and retrieval from picsum.photos with customizable parameters like dimensions, filters, and output formats.
    1
    -

Appeared in Searches