Skip to main content
Glama
deenesjakoruzh
yorifuji

MCP iOS Simulator Screenshot

by yorifuji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Captura de pantalla del simulador MCP iOS

Un servidor que captura capturas de pantalla del Simulador de iOS utilizando el Protocolo de contexto de modelo (MCP).

Descripción general

Este proyecto implementa un servidor de protocolo MCP que captura la pantalla actual del Simulador de iOS y la guarda en un directorio específico.

Related MCP server: Screeny MCP Server

Configuración

Código Cline y Roo

Para Cline y Roo Code, el formato básico es:

{
  "mcpServers": {
    "mcp-ios-simulator-screenshot": {
      "command": "npx",
      "args": ["-y", "mcp-ios-simulator-screenshot"]
    }
  }
}

Si clona el repositorio, puede utilizar la siguiente configuración:

{
  "mcpServers": {
    "mcp-ios-simulator-screenshot": {
      "command": "node",
      "args": ["/path/to/mcp-ios-simulator-screenshot/build/index.js"]
    }
  }
}

Cursor, Claude Desktop

Para Cursor y Claude Desktop, debe especificar --output-dir y el directorio de salida:

{
  "mcpServers": {
    "mcp-ios-simulator-screenshot": {
      "command": "npx",
      "args": [
        "mcp-ios-simulator-screenshot",
        "--output-dir",
        "/path/to/your/output/directory"
      ]
    }
  }
}

Parámetros de la herramienta MCP

obtener_captura_de_pantalla

Captura una captura de pantalla del Simulador de iOS y la guarda en el directorio especificado.

Parámetro

Tipo

Descripción

Valor predeterminado

nombre_de_archivo_de_salida

cadena

Nombre del archivo de salida

marca de tiempo.png

nombre_del_directorio_de_salida

cadena

Nombre del subdirectorio para capturas de pantalla

.capturas de pantalla

cambiar el tamaño

booleano

Si desea cambiar el tamaño de la imagen a aproximadamente tamaño VGA

verdadero

ancho máximo

entero

Ancho máximo para redimensionar (píxeles)

640

id_del_dispositivo

cadena

Especificar un dispositivo simulador

dispositivo arrancado

Formato de salida

En caso de éxito:

{
  "success": true,
  "message": "iOS Simulator screenshot saved successfully",
  "filePath": ".screenshots/simulator_2025-04-10T16-51-16-755Z.png",
  "metadata": {
    "width": 1170,
    "height": 2532,
    "format": "png",
    "size": 382946,
    "timestamp": "2025-04-10T16:51:16.755Z"
  },
  "serverConfig": {
    "commandLineArgs": {
      "outputDir": "/Users/username/Desktop" // Only included when --output-dir is specified
    }
  }
}

Nota: El campo serverConfig.commandLineArgs.outputDir solo se incluye en la respuesta cuando se especifica el parámetro --output-dir al iniciar el servidor.

{
  "success": false,
  "message": "Error capturing iOS Simulator screenshot: [error message]",
  "error": {
    "code": "ENOENT",
    "command": "xcrun simctl io booted screenshot --type=png -",
    "stderr": "No matching devices found."
  }
}

Solución de problemas

  • Si no puede capturar capturas de pantalla :

    • Comprueba si el simulador de iOS se está ejecutando

    • Compruebe si las herramientas de línea de comandos de Xcode están instaladas

    • Compruebe si el comando xcrun simctl io booted screenshot se puede ejecutar directamente

  • Si ocurren errores de permiso :

    • Comprueba si tienes permisos de escritura para el directorio de salida

Requisitos

  • Node.js 16.0.0 o superior

  • macOS (se requiere simulador de iOS)

  • Herramientas de línea de comandos de Xcode

Pila de tecnología

  • Mecanografiado

  • Node.js

  • Kit de desarrollo de software de MCP (@modelcontextprotocol/sdk)

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Otros idiomas

Available Tools

1 tool
get_screenshotC

Capture a screenshot from iOS Simulator

ParametersJSON Schema
NameRequiredDescriptionDefault
output_filenameNoOutput filename (if not specified, timestamp.png will be used)
output_directory_nameNoSubdirectory name for screenshots (if not specified, .screenshots will be used).screenshots
resizeNoWhether to resize the image to approximately VGA size
max_widthNoMaximum width for resizing (pixels)
device_idNoSpecify a simulator device (if not specified, the booted device will be used)

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 full burden for behavioral disclosure. 'Capture a screenshot' implies a read operation, but it doesn't specify whether this requires specific simulator states, permissions, or has side effects. The description lacks information about error conditions, what happens if no device is booted, or the format/location of output beyond what's in parameter descriptions.

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 that states the core purpose without unnecessary words. It's appropriately sized for a straightforward tool and gets directly to the point. Every word earns its place in conveying the essential function.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. While the purpose is clear, it lacks important behavioral context about how the tool operates, what it returns, error handling, and dependencies. The description doesn't compensate for the absence of structured metadata that would help an agent understand the tool's behavior and constraints.

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?

With 100% schema description coverage, all parameters are well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema descriptions. This meets the baseline expectation when schema coverage is complete, but doesn't provide extra semantic context.

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 ('Capture') and target resource ('screenshot from iOS Simulator'), making the purpose immediately understandable. It lacks sibling differentiation, but since there are no sibling tools, this doesn't reduce clarity. The description is specific enough to distinguish this from other potential screenshot tools.

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, prerequisites, or context. It simply states what the tool does without indicating appropriate scenarios or limitations. While there are no sibling tools to differentiate from, the description offers no usage context whatsoever.

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 observedget_screenshot
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clearly defined, making it impossible for an agent to misselect between non-existent alternatives.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'get_screenshot' follows a clear verb_noun pattern, which would be consistent if more tools existed.

Tool Count2/5

A single tool is too few for most practical server purposes, as it severely limits functionality and flexibility. While the server's name suggests a focused domain (iOS Simulator screenshots), one tool feels thin and incomplete for even basic operations like listing simulators or managing screenshots.

Completeness2/5

The tool surface is severely incomplete for the implied domain of iOS Simulator interactions. It only provides screenshot capture, with obvious gaps such as listing available simulators, starting/stopping simulators, or managing screenshot files, which are essential for a coherent workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches