MCP AppleScript
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMEOUT | No | Script execution timeout in seconds. | 30 |
| ALLOWED_APPS | No | Comma-separated list of allowed applications (case-insensitive). Use '*' to allow all applications (default), or an empty string to block all. | * |
| BLOCK_DANGEROUS | No | Enable or disable dangerous pattern detection (e.g., shell scripts, system control, file system access). | 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusA | Returns the list of allowed apps and whether dangerous command blocking is enabled. |
| run_applescriptA | Execute AppleScript commands on macOS. Use 'tell application "AppName"' to control apps. Multi-line scripts supported. Returns plain text output, truncated to 10,000 chars for large results. |
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 2 tools
The two tools have completely distinct purposes: run_applescript executes scripts and status returns configuration. No ambiguity in choice.
Both tools follow a consistent snake_case verb_noun pattern ('run_applescript' and 'status'), making naming predictable.
With only 2 tools, the server feels under-scoped for a typical CLI execution domain, which usually expects 3-15 tools for full interaction.
The domain of AppleScript execution is incompletely covered; missing tools for listing scripts, managing permissions, or retrieving error details leave agents with limited workflows.