Coyote MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_applescriptC | Executes an AppleScript command using osascript on macOS. |
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, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only a single tool, naming consistency is inherently perfect; there are no other tool names to compare it against, so no inconsistencies can arise.
A single tool is generally too few for most server purposes, as it limits functionality and suggests a very narrow scope. While it might be appropriate for a minimal utility, it often feels thin and incomplete for broader use cases.
The server's domain appears to be AppleScript execution on macOS, but with only one tool, there are significant gaps; for example, there are no tools for validating scripts, handling errors, or managing script files, making the surface severely incomplete for typical workflows.