Skip to main content
Glama
enesjakozh
noahlozevski

MCP-IDB

by noahlozevski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

mcp-idb

Facebook의 iOS 개발 브릿지(idb)를 위한 MCP 서버 통합.

개요

이 패키지는 MCP(Model Context Protocol) 와 Facebook의 idb(iOS Development Bridge) 간의 통합을 제공하여 MCP를 통해 자동화된 iOS 기기 관리 및 테스트 실행을 가능하게 합니다.

서버를 시작합니다:

지엑스피1

Related MCP server: iOS simulators MCP

필수 조건

idb 설치

idb를 설치하려면:

brew tap facebook/fb
brew install idb-companion

# verify installation
idb

자세한 내용은 공식 idb GitHub 저장소를 방문하세요.

구성

mcp-config.json 설정

MCP 구성에서 idb를 사용하려면 mcp-config.json 에 다음을 추가하세요.

{
  "mcpServers": {
    "idb": {
      "command": "npx",
      "args": ["-y", "@noahlozevski/idb"]
    }
  }
}

예시 사용 사례는 다음과 같습니다.

  • 자동화된 테스트 개발

  • 스크린샷 테스트

  • 자동화된 상호작용("화면의 홈 버튼을 탭하세요")

  • 애플리케이션 설치/제거

개발

코드 포맷팅

이 프로젝트에서는 Prettier를 사용하여 코드 서식을 지정합니다. 코드 서식을 지정하려면 다음을 수행하세요.

npm run format        # Format all files

포맷 구성은 프로젝트 루트의 .prettierrc 에서 찾을 수 있습니다.

문제 해결

일반적인 문제 및 해결 방법:

  1. idb companion을 찾을 수 없습니다 . Homebrew를 통해 idb-companion이 설치되어 있는지 확인하세요.

  2. 장치가 감지되지 않음 : iOS 장치가 다음 사항을 확인하세요.

    • USB를 통해 연결됨

    • 컴퓨터에서 신뢰됨

    • 개발자 모드가 활성화되어 있나요?

기여하다

이 패키지를 변경할 때는 표준 MCP 기여 지침을 따르세요.

특허

이 프로젝트는 모바일 제어 평면(MCP)의 일부이며 Amazon의 내부 라이선스 정책을 따릅니다.

Available Tools

1 tool
idbD
ParametersJSON Schema
NameRequiredDescriptionDefault
commandYesThe IDB command to execute (e.g., list-apps, screenshot, etc.). - For a full list of commands, run 'idb help'. - For help with a specific command, run 'idb <command> --help'. To interact with the device (simulator): IMPORTANT: Always try using the 'idb ui describe-all' command to identify buttons before dispatching UI actions. If that doesn't work, try using the following commands: - **Tap** - **Command:** 'idb ui tap X Y [--duration DURATION]' - **Description:** Simulates a tap at the given screen coordinates. Optionally, you can set the tap's duration. - **Swipe** - **Command:** 'idb ui swipe X_START Y_START X_END Y_END [--delta STEP_SIZE]' - **Description:** Simulates a swipe gesture from the start point to the end point. By default, the swipe moves in steps of 10 points; use '--delta' to change the step size. - **Press a Button** - **Command:** 'idb ui button {APPLE_PAY, HOME, LOCK, SIDE_BUTTON, SIRI} [--duration DURATION]' - **Description:** Simulates pressing a specified hardware button. The press duration can be adjusted with the '--duration' flag. - **Inputting Text** - **Command:** 'idb ui text "some text"' - **Description:** Types the provided text string into the target device. - **Key Events** - **Single Key:** 'idb ui key KEYCODE [--duration DURATION]' - **Key Sequence:** 'idb ui key-sequence KEYCODE1 KEYCODE2 ...' - **Description:** Simulates key press events. Use the single key command for one key press (with an optional duration) or the key sequence command for multiple sequential key events. **Frame and Coordinates in idb ui describe-all:** The output from 'idb ui describe-all' provides detailed layout information for each UI element. Each element includes a 'frame' object with: - **x and y:** The coordinates of the element's top-left corner relative to the device screen. - **width and height:** The dimensions of the element. Additionally, an 'AXFrame' string presents this data in a human-readable format like '{{x, y}, {width, height}}'. These values allow you to determine an element's position—commonly by calculating its center (x + width/2, y + height/2) for precise interactions. For instance, in the sample output, the "More, tab, 4 of 4" button has a frame starting at x=330, y=876.33 with a width of 110 and height of 45.67. A tap command such as 'idb ui tap 375 880' (which targets near the element's center) successfully triggers the button.
optionsNoOptional arguments for the IDB command

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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 observedidb
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

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'idb' stands alone with no other tools to confuse it with, making disambiguation perfect by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'idb' is a standalone identifier with no pattern deviations or mixing of conventions.

Tool Count2/5

A single tool with no description makes it difficult to assess the server's purpose, but one tool is generally too few for meaningful functionality unless it's a trivial utility. Without context, this feels insufficient for most domains, suggesting a mismatch in scope.

Completeness1/5

With only one tool and no description, it's impossible to infer the domain or assess coverage. There are likely significant gaps, as a single tool cannot provide CRUD/lifecycle coverage for any non-trivial purpose, making the surface severely incomplete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches