Scenic MCP
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 |
|---|---|
| connect_scenicC | Test connection to a Scenic application via TCP server |
| get_scenic_statusB | Check the status of the Scenic TCP connection |
| send_keysC | Send keyboard input to the connected Scenic application |
| send_mouse_moveC | Move mouse cursor to specific coordinates |
| send_mouse_clickC | Click mouse at specific coordinates |
| inspect_viewportB | Inspect the Scenic viewport to see what's currently displayed |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: connection testing, status checking, viewport inspection, keyboard input, mouse clicking, and mouse movement. The descriptions make it easy to differentiate between these functions, eliminating any ambiguity.
All tools follow a consistent verb_noun pattern with underscores (e.g., connect_scenic, get_scenic_status, inspect_viewport). The naming is predictable and readable throughout the set, with no deviations in style.
With 6 tools, this server is well-scoped for interacting with a Scenic application via TCP. Each tool earns its place by covering essential functions like connection management, input simulation, and display inspection, without being too sparse or bloated.
The toolset provides solid coverage for basic Scenic application interaction, including connection, status, input, and display. A minor gap exists in not having tools for more advanced interactions like drag-and-drop or multi-touch gestures, but core workflows are well-supported.