osascript MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OSASCRIPT_TIMEOUT | No | スクリプト実行タイムアウト（ミリ秒） | 30000 |
| OSASCRIPT_LOG_SCRIPTS | No | スクリプトをログ出力するか | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.