CrestronMCP client
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CrestronMCP clientturn on the projector in room A"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CrestronMCP client
Control a Crestron 4-Series AV system from Claude, in natural language. This is the
client half of CrestronMCP: an MCP server
that connects Claude (Desktop or Code) to a processor running the CrestronMCP modules,
exposing the system as MCP tools over stdio. It speaks the CrestronMCP text protocol
(see PROTOCOL.md) over TCP, with secure-key + TLS authentication.
The client is free. Controlling a processor requires that processor to be licensed (or on a free trial) — see Licensing. One processor licence is AUD $249 (inc GST); each processor also gets three free 1-week trials. Get a licence at https://solutionav.com.au/crestron-mcp/.
Install
Claude Desktop (recommended)
Download crestron-mcp.mcpb from https://solutionav.com.au/crestron-mcp/ and open it
(or Settings → Extensions → Install). Enter the processor's address and its secure key
(shown on the MCP Server Config module's Key output); the port defaults to 50794.
Claude Code / other MCP hosts
No download needed — run it straight from npm:
claude mcp add crestron \
--env CRESTRON_HOST=10.0.1.38 \
--env CRESTRON_KEY=<the processor's secure key> \
-- npx -y crestron-mcpRelated MCP server: claude-ssh-mcp
Configuration
Resolved low-to-high: config.json next to the entry, environment variables, then CLI
args (<host> [port]).
Env | Meaning |
| processor IP / hostname (required) |
| TCP port (default |
| secure key (mode 2); enables TLS + authentication |
| password (mode 1 only) |
| force TLS without a key |
Tools
discover_crestron_system, list_crestron_rooms, list_crestron_devices,
query_crestron_device, get_crestron_time, control_crestron_device,
set_crestron_devices, pulse_crestron_device, ramp_crestron_device,
cancel_crestron_device, get_room_status, activate_crestron_license,
get_crestron_license_status, start_crestron_trial.
See AGENT_GUIDE.md for how an assistant should use them (timing,
scenes, ramps, nudge-not-nag licensing etiquette).
Licensing
The processor must be licensed before it accepts control or query commands. If it isn't, every tool returns guidance that includes the processor's activation code (its MAC). Two ways forward, both in chat:
Free trial —
start_crestron_trial(no payment; up to 3 × 1 week per processor).Buy — get a key for that MAC at https://solutionav.com.au/crestron-mcp/, paste it in chat, and the assistant calls
activate_crestron_license.
The licence is stored on the processor (bound to its MAC), so it persists across reboots and covers every client. A purchased key only works on that one processor, so it's safe to receive in chat.
Develop
npm install
npm run build # tsc -> dist/
npm start # node dist/index.js
npm run mcpb # build the Claude Desktop .mcpb (needs bun)License
MIT — see LICENSE. (The client is open; the product is the per-processor
licence on the box.)
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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/SolutionAVAutomation/crestron-mcp-client'
If you have feedback or need assistance with the MCP directory API, please join our Discord server