Skip to main content
Glama
enesjakozh
kazuph

mcp-screenshot

by kazuph
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

MCP Screenshot

An MCP server that captures screenshots and performs OCR text recognition.

Features

  • Screenshot capture (left half, right half, full screen)

  • OCR text recognition (supports Japanese and English)

  • Multiple output formats (JSON, Markdown, vertical, horizontal)

Related MCP server: PeepIt MCP

OCR Engines

This server uses two OCR engines:

  1. yomitoku

    • Primary OCR engine

    • High-accuracy Japanese text recognition

    • Runs as an API server

  2. Tesseract.js

    • Fallback OCR engine

    • Used when yomitoku is unavailable

    • Supports both Japanese and English recognition

Installation

npx -y @kazuph/mcp-screenshot

Claude Desktop Configuration

Add the following configuration to your claude_desktop_config.json:

{
  "mcpServers": {
    "screenshot": {
      "command": "npx",
      "args": ["-y", "@kazuph/mcp-screenshot"],
      "env": {
        "OCR_API_URL": "http://localhost:8000"  // yomitoku API base URL
      }
    }
  }
}

Environment Variables

Variable Name

Description

Default Value

OCR_API_URL

yomitoku API base URL

http://localhost:8000

Usage Example

You can use it by instructing Claude like this:

Please take a screenshot of the left half of the screen and recognize the text in it.

Tool Specification

capture

Takes a screenshot and performs OCR.

Options:

  • region: Screenshot area ('left'/'right'/'full', default: 'left')

  • format: Output format ('json'/'markdown'/'vertical'/'horizontal', default: 'markdown')

License

MIT

Author

kazuph

Available Tools

1 tool
captureA

Captures a screenshot of the specified region and performs OCR. Options:

  • region: 'left'/'right'/'full' (default: 'left')

  • format: 'json'/'markdown'/'vertical'/'horizontal' (default: 'markdown') The screenshot is saved to a dated directory in Downloads.

ParametersJSON Schema
NameRequiredDescriptionDefault
formatNomarkdown
regionNoleft

TDQS

A4.2/5.0
Behavior4/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 effectively describes key behaviors: the tool captures screenshots, performs OCR, saves files to a dated directory in Downloads, and provides default values for parameters. However, it misses details like error handling or performance characteristics.

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 front-loaded with the core purpose, followed by a bulleted list of options for clarity. Every sentence earns its place by providing essential information without redundancy, making it efficient and well-structured.

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

Completeness4/5

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

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is mostly complete. It covers purpose, parameters, and behavioral aspects like file saving. A minor gap is the lack of detail on OCR output or error cases, but overall it suffices for informed use.

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

Parameters4/5

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

The schema has 0% description coverage, so the description must compensate. It adds meaningful context by explaining what 'region' and 'format' control, including their allowed values and defaults. This goes beyond the schema's enum lists, though it could elaborate on the effects of each format option.

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 tool's purpose with specific verbs ('captures a screenshot', 'performs OCR') and resources ('specified region'), making it immediately understandable. It distinguishes the tool's dual functionality of screenshot capture and OCR processing, which is comprehensive for its domain.

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

Usage Guidelines3/5

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

The description implies usage through the mention of options like region and format, but does not explicitly state when to use this tool versus alternatives. Since there are no sibling tools, this is less critical, but it lacks guidance on scenarios or prerequisites for effective use.

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. 1 tool updatev1.0.0
    • First observedcapture
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'capture' has a clearly defined and distinct purpose.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'capture' is clear and descriptive.

Tool Count2/5

One tool is too few for most server purposes, as it limits functionality and flexibility. While the tool is feature-rich with options, a single tool feels thin and may not cover all potential use cases for a screenshot utility.

Completeness3/5

The tool provides core screenshot and OCR functionality, but there are notable gaps such as no tools for managing saved screenshots (e.g., list, delete), adjusting OCR settings, or handling different output formats beyond the provided options. The surface is functional but incomplete.

Maintenance

ActivityInactive
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

  • PeepIt MCP

    MantisWare
    A
    license
    A
    quality
    D
    maintenance
    Enables AI agents to capture and analyze screenshots of macOS applications, windows, or the entire screen using local (Ollama) or cloud-based AI vision models, with non-intrusive, fast screen capture via Apple's ScreenCaptureKit.
    3
    15
    2
    MIT

  • MCP Screen Text

    ikhide
    F
    license
    B
    quality
    D
    maintenance
    Provides screen capture and optical character recognition (OCR) capabilities for entire displays or specific application windows. It enables users to list running applications, take screenshots, and extract text from images using multi-language support.
    5
    1
    -

  • macOS MCP Server

    alexlock1
    A
    license
    A
    quality
    D
    maintenance
    Enables interaction with macOS system features including file dialogs, clipboard management, Finder integration, and system notifications. It also provides tools for taking screenshots, processing images, managing PDFs, and interacting with the Apple Notes app.
    25
    1
    MIT

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/kazuph/mcp-screenshot'

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