Skip to main content
Glama
deenesjakoruzh
kshern

image-tools-mcp

by kshern
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

画像ツール MCP

鍛冶屋のバッジ

URL とローカル ファイル ソースの両方をサポートし、画像のサイズを取得して画像を圧縮するためのモデル コンテキスト プロトコル (MCP) サービス。

中文档

特徴

  • URLから画像のサイズを取得する

  • ローカルファイルから画像のサイズを取得する

  • TinyPNG API を使用して URL から画像を圧縮する

  • TinyPNG APIを使用してローカル画像を圧縮する

  • 画像をさまざまな形式（webp、jpeg/jpg、png）に変換します

  • 幅、高さ、タイプ、MIMEタイプ、圧縮情報を返します。

結果例

例の結果1例の結果2

figmaのURLからダウンロードして圧縮する例の結果3

Related MCP server: test-1

使用法

MCPサービスとして利用

このサービスは、次の 5 つのツール機能を提供します。

  1. get_image_size - リモート画像のサイズを取得する

  2. get_local_image_size - ローカル画像のサイズを取得する

  3. compress_image_from_url - TinyPNG API を使用してリモート画像を圧縮する

  4. compress_local_image - TinyPNG API を使用してローカル画像を圧縮する

  5. figma - Figma API から画像リンクを取得し、TinyPNG API を使用して圧縮します。

クライアント統合

このMCPサービスを利用するには、MCPクライアントから接続する必要があります。以下に、様々なクライアントとの統合方法の例を示します。

Claude Desktopでの使用

  1. claude.ai/downloadからClaude Desktopをインストールします。

  2. TinyPNG APIキーを取得: TinyPNGにアクセスしてAPIキーを取得します

  3. 構成ファイルを編集して、Claude Desktop がこの MCP サーバーを使用するように設定します。

{
  "mcpServers": {
    "image-tools": {
      "command": "npx",
      "args": ["image-tools-mcp"],
      "env": {
        "TINIFY_API_KEY": "<YOUR_TINIFY_API_KEY>",
        "FIGMA_API_TOKEN": "<YOUR_FIGMA_API_TOKEN>"
      }
    }
  }
}

  1. Claudeデスクトップを再起動します

  2. Claude に画像のサイズを取得するよう依頼します。「この画像のサイズを教えていただけますか: https://example.com/image.jpg 」

  3. クロードに画像を圧縮するように依頼します。「この画像を圧縮できますか: https://example.com/image.jpg 」

  4. Claude にローカル画像を圧縮するように依頼します。「この画像を圧縮できますか: D:/path/to/image.png」

  5. Claude にローカル画像フォルダを圧縮するように依頼します。「このフォルダを圧縮できますか: D:/imageFolder」

  6. Claude に Figma API から画像リンクを取得するように依頼します。「Figma API から画像リンクを取得できますか: https://www.figma.com/file/XXXXXXX 」

MCPクライアントライブラリの使用

import { McpClient } from "@modelcontextprotocol/client";

// Initialize the client
const client = new McpClient({
  transport: "stdio" // or other transport options
});

// Connect to the server
await client.connect();

// Get image dimensions from URL
const urlResult = await client.callTool("get_image_size", {
  options: {
    imageUrl: "https://example.com/image.jpg"
  }
});
console.log(JSON.parse(urlResult.content[0].text));
// Output: { width: 800, height: 600, type: "jpg", mime: "image/jpeg" }

// Get image dimensions from local file
const localResult = await client.callTool("get_local_image_size", {
  options: {
    imagePath: "D:/path/to/image.png"
  }
});
console.log(JSON.parse(localResult.content[0].text));
// Output: { width: 1024, height: 768, type: "png", mime: "image/png", path: "D:/path/to/image.png" }

// Compress image from URL
const compressUrlResult = await client.callTool("compress_image_from_url", {
  options: {
    imageUrl: "https://example.com/image.jpg",
    outputFormat: "webp" // Optional: convert to webp, jpeg/jpg, or png
  }
});
console.log(JSON.parse(compressUrlResult.content[0].text));
// Output: { originalSize: 102400, compressedSize: 51200, compressionRatio: "50.00%", tempFilePath: "/tmp/compressed_1615456789.webp", format: "webp" }

// Compress local image
const compressLocalResult = await client.callTool("compress_local_image", {
  options: {
    imagePath: "D:/path/to/image.png",
    outputPath: "D:/path/to/compressed.webp", // Optional
    outputFormat: "image/webp" // Optional: convert to image/webp, image/jpeg, or image/png
  }
});
console.log(JSON.parse(compressLocalResult.content[0].text));
// Output: { originalSize: 102400, compressedSize: 51200, compressionRatio: "50.00%", outputPath: "D:/path/to/compressed.webp", format: "webp" }

// Fetch image links from Figma API

const figmaResult = await client.callTool("figma", {
  options: {
    figmaUrl: "https://www.figma.com/file/XXXXXXX"
  }
});
console.log(JSON.parse(figmaResult.content[0].text));
// Output: { imageLinks: ["https://example.com/image1.jpg", "https://example.com/image2.jpg"] }

### Tool Schemas

#### get_image_size

```typescript
{
  options: {
    imageUrl: string // URL of the image to retrieve dimensions for
  }
}

ローカル画像サイズの取得

{
  options: {
    imagePath: string; // Absolute path to the local image file
  }
}

URLから画像を圧縮する

{
  options: {
    imageUrl: string // URL of the image to compress
    outputFormat?: "image/webp" | "image/jpeg" | "image/jpg" | "image/png" // Optional output format
  }
}

ローカル画像を圧縮する

{
  options: {
    imagePath: string // Absolute path to the local image file
    outputPath?: string // Optional absolute path for the compressed output image
    outputFormat?: "image/webp" | "image/jpeg" | "image/jpg" | "image/png" // Optional output format
  }
}

フィグマ

{
  options: {
    figmaUrl: string; // URL of the Figma file to fetch image links from
  }
}

変更履歴

  • 2025-05-12: 2 倍の画像スケーリングなどの追加パラメータをサポートするように Figma API を更新しました。

技術的実装

このプロジェクトは次のライブラリ上に構築されています:

環境変数

  • TINIFY_API_KEY - 画像圧縮機能に必要です。TinyPNGからAPIキーを取得してください。

    • 指定されていない場合、圧縮ツール（ compress_image_from_urlとcompress_local_image ）は登録されません。

  • FIGMA_API_TOKEN - Figma APIから画像リンクを取得するために必要です。FigmaからAPIトークンを取得してください。

    • 指定しない場合、Figmaツール（ figma ）は登録されません。

注: 基本的な画像寸法ツール ( get_image_sizeおよびget_local_image_size ) は、API キーに関係なく常に利用できます。

ライセンス

マサチューセッツ工科大学

Available Tools

2 tools
get_image_sizeC

Get the size of an image from URL

ParametersJSON Schema
NameRequiredDescriptionDefault
optionsYesOptions for retrieving image size

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks details on performance (e.g., network timeouts, rate limits), error handling (e.g., invalid URLs, unsupported formats), or output format (e.g., dimensions in pixels). This leaves significant gaps for a tool that performs network operations.

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

Conciseness5/5

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

The description is a single, direct sentence with zero wasted words. It front-loads the core purpose ('Get the size of an image') and efficiently specifies the source ('from URL'). Every word earns its place, making it highly concise and well-structured.

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

Completeness2/5

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

Given the tool's network-based operation and lack of annotations or output schema, the description is incomplete. It doesn't address critical context like what 'size' means (e.g., dimensions, file size), potential errors, or response format. For a tool with no structured output documentation, this leaves too much unspecified.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents the single parameter 'imageUrl'. The description adds no additional semantic context beyond implying the URL is for an image, which is already clear from the parameter name. This meets the baseline for high schema coverage but doesn't enhance understanding.

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

Purpose4/5

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

The description clearly states the action ('Get the size') and resource ('an image from URL'), making the purpose immediately understandable. It distinguishes from the sibling tool 'get_local_image_size' by specifying the image source as 'from URL' rather than local. However, it doesn't explicitly contrast with the sibling, so it's not a perfect 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus its sibling 'get_local_image_size'. There's no mention of prerequisites, alternative scenarios, or exclusion criteria. The agent must infer usage from the name and description alone without explicit direction.

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

get_local_image_sizeC

Get the size of a local image

ParametersJSON Schema
NameRequiredDescriptionDefault
optionsYesOptions for retrieving local image size

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't add context beyond the basic action—missing details like error handling, performance implications, or what the output looks like (e.g., dimensions in pixels). This leaves significant gaps for a tool that interacts with local files.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste, front-loading the core purpose without unnecessary details. It's appropriately sized for a simple tool, making it easy to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool that reads local files. It doesn't explain the return value (e.g., width and height), error cases, or security considerations, leaving the agent with insufficient context to use it effectively beyond the basic parameter.

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

Parameters3/5

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

The input schema has 100% description coverage, documenting the 'imagePath' parameter as an absolute path. The description doesn't add any meaning beyond this, such as format examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting without extra value from the description.

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

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'size of a local image', making the purpose specific and understandable. However, it doesn't explicitly differentiate from its sibling 'get_image_size', which might handle remote images or have different scope, leaving room for ambiguity in sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as its sibling 'get_image_size'. It lacks context on prerequisites, exclusions, or specific scenarios, offering only a basic statement of function without usage instructions.

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.

  1. 2 tool updatesv1.0.0
    • First observedget_image_size
    • First observedget_local_image_size
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
Disambiguation2/5

The two tools have overlapping purposes—both retrieve image sizes—with only the source (URL vs. local) differing. This creates ambiguity as an agent might misselect between them if the input context is unclear, such as when 'image' could refer to either type. The descriptions help slightly by specifying the source, but the core functionality is identical, leading to potential confusion.

Naming Consistency5/5

The tool names follow a consistent verb_noun pattern with 'get_image_size' and 'get_local_image_size', both using snake_case and starting with 'get'. This predictability makes it easy for an agent to understand the naming convention and infer tool purposes without deviation or mixed styles.

Tool Count2/5

With only 2 tools, the server feels thin and under-scoped for an 'image-tools' domain, which typically implies a broader set of operations like resizing, converting, or analyzing images. The limited count suggests incomplete coverage, as basic image manipulation tasks beyond size retrieval are missing, making it inadequate for comprehensive image handling.

Completeness2/5

The tool set is severely incomplete for an image processing domain, covering only size retrieval from two sources. There are significant gaps in common operations such as resizing, cropping, format conversion, or metadata extraction, which will likely cause agent failures when attempting typical image-related tasks. The surface lacks core functionality needed for a coherent image tools server.

Maintenance

ActivityInactive
ResponsivenessNo issues

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

Appeared in Searches

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/kshern/image-tools-mcp'

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