Skip to main content
Glama
Akira-Papa

osascript MCP Server

by Akira-Papa
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Local

osascript MCP Server

macOS の osascript（AppleScript / JavaScript for Automation）を実行できる MCP サーバーです。

特徴

  • AppleScript サポート: macOS のネイティブ AppleScript を実行

  • JXA サポート: JavaScript for Automation（JXA）を実行

  • 安全設計: ファイル削除コマンドのみブロック（その他は全て許可）

  • Desktop Extension 対応: .mcpb 形式でワンクリックインストール

Related MCP server: macOS GUI Control MCP

インストール

方法 1: MCPB ファイルから（推奨）

  1. .mcpb ファイルをダウンロード

  2. Claude Desktop にドラッグ＆ドロップ

  3. インストールを許可

方法 2: 手動設定

Claude Desktop の設定ファイル（~/Library/Application Support/Claude/claude_desktop_config.json）に追加:

{
  "mcpServers": {
    "osascript": {
      "command": "node",
      "args": ["/path/to/osascript-mcp/server/index.js"],
      "env": {
        "OSASCRIPT_TIMEOUT": "30000",
        "OSASCRIPT_LOG_SCRIPTS": "true"
      }
    }
  }
}

使用方法

AppleScript の実行

tell application "Finder" to get name of every disk

JXA（JavaScript）の実行

Application("System Events").processes().map(p => p.name())

許可される操作

以下の操作は全て許可されています：

シェルコマンド（削除以外）

do shell script "ls -la ~/Desktop"
do shell script "whoami"
do shell script "curl -s https://api.github.com"
do shell script "cat ~/.zshrc"

Finder 操作

tell application "Finder" to get name of every disk
tell application "Finder" to get every file of desktop
tell application "Finder" to open folder "Documents" of home

System Events

tell application "System Events" to get name of every process
tell application "System Events" to keystroke "hello"
tell application "System Events" to key code 36 -- Enter

アプリケーション制御

tell application "Safari" to get URL of current tab of window 1
tell application "Music" to get name of current track
tell application "Calendar" to get events of calendar 1

ブロックされる操作

以下の削除操作のみがブロックされます：

シェルでの削除

-- これらはブロックされます
do shell script "rm test.txt"
do shell script "rm -rf ~/test"
do shell script "rmdir testdir"

Finder での削除

-- これらはブロックされます
tell application "Finder" to delete file "test.txt" of desktop
move file "test.txt" to trash
empty trash

設定オプション

オプション

説明

デフォルト

timeout

スクリプト実行タイムアウト（ミリ秒）

30000

log_scripts

スクリプトをログ出力するか

true

開発

ビルド

# 依存関係インストール
npm install

# ローカルテスト
npm start

# MCPB パッケージ作成
npm install -g @anthropic-ai/mcpb
mcpb validate manifest.json
mcpb pack .

テスト

# 許可されるスクリプトのテスト
echo 'tell application "Finder" to get name of every disk' | node server/index.js

# サーバーの直接実行（デバッグ用）
node server/index.js

セキュリティ

このサーバーは「最小限のセキュリティ」設計を採用しています：

  • ✅ 許可: シェルコマンド（ls, curl, cat など）

  • ✅ 許可: System Events（keystroke, key code）

  • ✅ 許可: 全アプリケーションの制御

  • ❌ ブロック: rm, delete, trash などの削除操作

より厳格なセキュリティが必要な場合は、server/index.js の BLOCKED_PATTERNS を編集してください。

ライセンス

MIT

関連リンク

Available Tools

1 tool
osascriptA

Execute AppleScript or JavaScript for Automation (JXA) on macOS. Full access to system automation including shell commands, app control, and System Events. Only file deletion commands are blocked for safety.

ParametersJSON Schema
NameRequiredDescriptionDefault
scriptYesThe script to execute
languageNoScript language: AppleScript (default) or JavaScript for Automation (JXA)AppleScript

TDQS

A4/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 the tool's capabilities ('Full access to system automation'), constraints ('Only file deletion commands are blocked for safety'), and scope ('on macOS'), covering key behavioral traits like safety measures and system access without contradictions.

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 key capabilities and a safety constraint in just two sentences. Every sentence adds essential value without redundancy, making it highly 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 complexity (system automation with safety constraints), no annotations, and no output schema, the description provides good context on capabilities and limitations. However, it lacks details on error handling, output format, or execution environment, leaving some gaps for a high-risk tool.

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 already documents both parameters thoroughly. The description does not add specific meaning or examples beyond what the schema provides (e.g., script syntax or language details), meeting the baseline for high schema coverage.

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 ('Execute AppleScript or JavaScript for Automation') and the resource ('on macOS'), with explicit scope ('Full access to system automation including shell commands, app control, and System Events'). It distinguishes the tool's capabilities comprehensively without siblings to differentiate from.

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 for macOS automation tasks but does not provide explicit guidance on when to use this tool versus alternatives (e.g., other scripting tools or direct system commands). No exclusions or prerequisites are mentioned beyond the safety block on file deletion.

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 update
    • First observedosascript
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clearly defined and distinct purpose: executing AppleScript or JavaScript for Automation on macOS.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'osascript' is straightforward and matches the server's purpose.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and can lead to dead ends in agent workflows. While the tool is powerful, the scope of macOS automation suggests more specialized tools (e.g., for specific apps or tasks) would be appropriate.

Completeness2/5

The tool surface is severely incomplete for macOS automation. It lacks coverage for common operations like querying system information, managing files (beyond the blocked deletion), controlling specific applications, or handling events, which are typical in automation domains.

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

  • macOS GUI Control MCP

    Akira-Papa
    A
    license
    A
    quality
    D
    maintenance
    Enables comprehensive control over macOS GUI elements including mouse, keyboard, window management, and screen capture. It allows for automated system interactions and script execution while maintaining safety by blocking potentially destructive deletion commands.
    19
    34
    5
    MIT

  • MCP AppleScript

    pietz
    A
    license
    A
    quality
    C
    maintenance
    Enables Large Language Models to automate macOS applications and execute AppleScript commands through natural language. It features built-in security protections including application allowlists and dangerous pattern detection to prevent unauthorized or risky system operations.
    2
    MIT

  • AppleScript MCP

    Hassanali4
    A
    license
    A
    quality
    C
    maintenance
    Enables full control of macOS by executing AppleScript commands through an MCP server, allowing automation of tasks, application control, and system management.
    1
    123
    15
    MIT

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/Akira-Papa/osascript-MCP-1'

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