roomtalk-for-crestron 1.20.0 → 1.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENT_GUIDE.md CHANGED
@@ -52,7 +52,7 @@ claude mcp add crestron \
52
52
  -e CRESTRON_HOST=<processor-ip> \
53
53
  -e CRESTRON_KEY=<secure-key> \
54
54
  -s user \
55
- -- /path/to/mcp-for-crestron-<platform>
55
+ -- /path/to/roomtalk-for-crestron-<platform>
56
56
  ```
57
57
 
58
58
  Or a project `.mcp.json`:
@@ -61,7 +61,7 @@ Or a project `.mcp.json`:
61
61
  {
62
62
  "mcpServers": {
63
63
  "crestron": {
64
- "command": "/path/to/mcp-for-crestron-<platform>",
64
+ "command": "/path/to/roomtalk-for-crestron-<platform>",
65
65
  "env": { "CRESTRON_HOST": "<processor-ip>", "CRESTRON_KEY": "<secure-key>" }
66
66
  }
67
67
  }
package/LABEL_GUIDE.md CHANGED
@@ -1,6 +1,6 @@
1
- # Writing labels for MCP for Crestron
1
+ # Writing labels for RoomTalk for Crestron
2
2
 
3
- The labels you set on the MCP for Crestron modules are what the assistant knows about
3
+ The labels you set on the RoomTalk for Crestron modules are what the assistant knows about
4
4
  your system. It never sees your SIMPL program, only the room, category and label of
5
5
  each channel, plus the live values. A good label tells it what a channel is, how to
6
6
  drive it, and any rule it should follow. The assistant treats labels as the
package/OTHER_CLIENTS.md CHANGED
@@ -1,12 +1,12 @@
1
- # Using MCP for Crestron with other AI apps
1
+ # Using RoomTalk for Crestron with other AI apps
2
2
 
3
- MCP for Crestron is a standard MCP server that runs over stdio, so any app that can
3
+ The RoomTalk for Crestron client is a standard MCP server that runs over stdio, so any app that can
4
4
  launch an MCP server can use it, with any model that handles tool calls well. Claude
5
5
  Desktop has a one-click installer (the `.mcpb`). Everything else runs it from npm.
6
6
 
7
7
  Every setup needs the same three things:
8
8
 
9
- - the command `npx -y mcp-for-crestron@latest`
9
+ - the command `npx -y roomtalk-for-crestron@latest`
10
10
  - `CRESTRON_HOST`, the processor's IP address or hostname
11
11
  - `CRESTRON_KEY`, the processor's secure key, shown on the MCP Server Config module's
12
12
  `Key` output (setting it turns on encryption and secure authentication)
@@ -29,7 +29,7 @@ mcpServers:
29
29
  command: npx
30
30
  args:
31
31
  - -y
32
- - mcp-for-crestron@latest
32
+ - roomtalk-for-crestron@latest
33
33
  env:
34
34
  CRESTRON_HOST: "10.0.1.38"
35
35
  CRESTRON_KEY: "${CRESTRON_KEY}"
@@ -48,7 +48,7 @@ Restart LibreChat after changing either file, then pick the Crestron tools in a
48
48
  claude mcp add crestron \
49
49
  --env CRESTRON_HOST=10.0.1.38 \
50
50
  --env CRESTRON_KEY=<the processor's secure key> \
51
- -- npx -y mcp-for-crestron@latest
51
+ -- npx -y roomtalk-for-crestron@latest
52
52
  ```
53
53
 
54
54
  ## Any other MCP host
@@ -60,7 +60,7 @@ Most hosts take a JSON block like this one:
60
60
  "mcpServers": {
61
61
  "crestron": {
62
62
  "command": "npx",
63
- "args": ["-y", "mcp-for-crestron@latest"],
63
+ "args": ["-y", "roomtalk-for-crestron@latest"],
64
64
  "env": {
65
65
  "CRESTRON_HOST": "10.0.1.38",
66
66
  "CRESTRON_KEY": "<the processor's secure key>"
package/README.md CHANGED
@@ -1,26 +1,26 @@
1
1
  # RoomTalk for Crestron client
2
2
 
3
- **RoomTalk for Crestron is the new name for MCP for Crestron.** Same client, same settings and tools; install with `npx -y roomtalk-for-crestron`.
3
+ RoomTalk for Crestron is the new name for MCP for Crestron; settings and tools are unchanged.
4
4
 
5
5
  Control a Crestron 4-Series AV system from Claude, in natural language. This is the
6
- client half of [MCP for Crestron](https://solutionav.com.au/crestron-mcp/): an MCP server
7
- that connects Claude (Desktop or Code) to a processor running the MCP for Crestron modules,
8
- exposing the system as MCP tools over stdio. It speaks the MCP for Crestron text protocol
6
+ client half of [RoomTalk for Crestron](https://solutionav.com.au/roomtalk-for-crestron/): an MCP server
7
+ that connects Claude (Desktop or Code) to a processor running the RoomTalk for Crestron modules,
8
+ exposing the system as MCP tools over stdio. It speaks the RoomTalk text protocol
9
9
  (see [`PROTOCOL.md`](PROTOCOL.md)) over TCP, with secure-key + TLS authentication.
10
10
 
11
- [![MCP for Crestron: controlling a boardroom from Claude in plain English](demo-poster.jpg)](https://solutionav.com.au/mcp-for-crestron/media/mcp-for-crestron-demo-full.mp4)
11
+ [![RoomTalk for Crestron: controlling a boardroom from Claude in plain English](demo-poster.jpg)](https://solutionav.com.au/roomtalk-for-crestron/media/mcp-for-crestron-demo-full.mp4)
12
12
 
13
- *Talk to your Crestron system in plain English. [Watch the full demo (1:19) »](https://solutionav.com.au/mcp-for-crestron/media/mcp-for-crestron-demo-full.mp4)*
13
+ *Talk to your Crestron system in plain English. [Watch the full demo (1:19) »](https://solutionav.com.au/roomtalk-for-crestron/media/mcp-for-crestron-demo-full.mp4)*
14
14
 
15
15
  The client is **free**. Controlling a processor requires that processor to be licensed
16
16
  (or on a free trial). See [Licensing](#licensing). One processor licence is AUD $249
17
17
  (inc GST); each processor also gets three free 1-week trials. Get a licence at
18
- <https://solutionav.com.au/crestron-mcp/>.
18
+ <https://solutionav.com.au/roomtalk-for-crestron/>.
19
19
 
20
20
  ## Install
21
21
 
22
22
  ### Claude Desktop (recommended)
23
- Download `mcp-for-crestron.mcpb` from <https://solutionav.com.au/crestron-mcp/> and open it
23
+ Download `roomtalk-for-crestron.mcpb` from <https://solutionav.com.au/roomtalk-for-crestron/> and open it
24
24
  (or Settings → Extensions → Install). Enter the processor's address and its secure key
25
25
  (shown on the MCP Server Config module's `Key` output); the port defaults to `50794`.
26
26
 
@@ -79,7 +79,7 @@ every tool returns guidance that includes the processor's **activation code (its
79
79
  Two ways forward, both in chat:
80
80
 
81
81
  - **Free trial**: `start_crestron_trial` (no payment; up to 3 × 1 week per processor).
82
- - **Buy**: get a key for that MAC at <https://solutionav.com.au/crestron-mcp/>, paste it
82
+ - **Buy**: get a key for that MAC at <https://solutionav.com.au/roomtalk-for-crestron/>, paste it
83
83
  in chat, and the assistant calls `activate_crestron_license`.
84
84
 
85
85
  The licence is stored **on the processor** (bound to its MAC), so it persists across
@@ -102,5 +102,5 @@ licence on the box.)
102
102
 
103
103
  ## Trademark
104
104
 
105
- Crestron is a registered trademark of Crestron Electronics, Inc.; MCP for Crestron is a
105
+ Crestron is a registered trademark of Crestron Electronics, Inc.; RoomTalk is a
106
106
  product of Solution AV Automation, not affiliated with or endorsed by Crestron.
@@ -13,7 +13,7 @@ import * as crypto from "node:crypto";
13
13
  /** Where customers buy a license, and where the client fetches free trials. Overridable via
14
14
  * env for testing (point at a local mock or the Stripe test-mode portal). The MAC is appended
15
15
  * as ?mac= so the storefront/trial is bound to this processor. */
16
- const PORTAL_URL = process.env.CRESTRON_PORTAL_URL || "https://solutionav.com.au/crestron-mcp/";
16
+ const PORTAL_URL = process.env.CRESTRON_PORTAL_URL || "https://solutionav.com.au/roomtalk-for-crestron/";
17
17
  const TRIAL_URL = process.env.CRESTRON_TRIAL_URL || "https://license.solutionav.com.au/trial";
18
18
  /** Host of the trial/licensing server, surfaced in the trial result so the assistant can say
19
19
  * where a trial came from. The fetch happens inside this client, below the tool boundary, so
@@ -459,7 +459,7 @@ export class CrestronConnection {
459
459
  return JSON.parse(response.slice(5));
460
460
  if (response.startsWith("ERROR:1000")) {
461
461
  return {
462
- error: "This processor's MCP for Crestron modules are too old for processor info (it needs " +
462
+ error: "This processor's modules are too old for processor info (it needs " +
463
463
  "modules 1.12.0 or later). Update the modules (load the latest MCPForCrestron.clz, " +
464
464
  "recompile and upload the program), then try again.",
465
465
  };
@@ -720,7 +720,7 @@ export class CrestronConnection {
720
720
  if (response.startsWith("ERROR:1000")) {
721
721
  return {
722
722
  success: false,
723
- error: "This processor's MCP for Crestron modules are too old for schedules. Update the modules " +
723
+ error: "This processor's modules are too old for schedules. Update the modules " +
724
724
  "(load the latest MCPForCrestron.clz, recompile and upload the program), then try again.",
725
725
  };
726
726
  }
@@ -747,7 +747,7 @@ export class CrestronConnection {
747
747
  if (response.startsWith("ERROR:1000")) {
748
748
  return {
749
749
  success: false,
750
- error: "This processor's MCP for Crestron modules are too old for saved presets (1.13.0 or later " +
750
+ error: "This processor's modules are too old for saved presets (1.13.0 or later " +
751
751
  "needed). Update the modules (load the latest MCPForCrestron.clz, recompile and upload the " +
752
752
  "program), then try again.",
753
753
  };
package/dist/index.js CHANGED
@@ -1,6 +1,6 @@
1
1
  #!/usr/bin/env node
2
2
  /**
3
- * MCP for Crestron client (Node/TypeScript)
3
+ * RoomTalk for Crestron client (Node/TypeScript)
4
4
  *
5
5
  * Exposes a Crestron 4-Series system to Claude over MCP. Connects to the
6
6
  * processor (or the simulator) using the text protocol in PROTOCOL.md.
@@ -45,7 +45,7 @@ Schedules: the processor can run actions on a schedule (once, daily, on chosen w
45
45
  Presets: a room may have presets the integrator built into the program, usually buttons named for a scene (such as "TV Time"); when one fits the request, press it rather than rebuilding it from individual devices. Owners can also save their own presets on the processor (for example "make a Reading preset with the lamp at 60% and the downlights at 75%"): build it from the room's devices as you would a scene, save it, and recall it by name when asked. Each saved preset belongs to one room, so every room can have its own "Evening": the room its devices are in unless the user names another, or the whole house when they ask for that or it spans rooms. A preset name has three scopes: one room's preset, the whole-house preset (room "house"), or every room (room "all", every room's preset of that name plus the whole-house one). Take the scope from the user's words: "turn the house off for the night" or "everything off" means every room, and "lounge evening", or a name while a current room is set, means that room. Nothing falls back to another scope; when the scope is unclear, or the room doesn't have that preset but somewhere else does, the processor says where it exists, and you ask a short question ("just the lounge, or the whole house?") before acting. If a save or recall reports clashes, tell the user which devices the same-named presets set differently and offer to make them agree. Whenever you save or re-save a preset, give each device the fade time from its name or description, as you would when setting it. When asked what presets a room has, give the integrator's preset buttons and the owner's saved presets as two groups; a saved preset reports whether it is active now. A scene you set up without saving is not kept after this chat, so never promise to remember it; offer to save it as a preset instead. A schedule can recall a saved preset. Some presets are on buttons the integrator programmed: the preset list marks them on_button, and a button finds its preset by name, so before deleting or renaming one of those, check with the user, because the button stops working. A button whose preset does not exist yet is listed under unassigned_buttons with its room; offer to create it in that room, using exactly that name.
46
46
 
47
47
  Honesty: if the processor reports it is unlicensed or on a trial, mention it once, do not nag.`;
48
- const server = new McpServer({ name: "crestron-control", version: "1.20.0" }, { instructions: OPERATING_BRIEF });
48
+ const server = new McpServer({ name: "crestron-control", version: "1.21.0" }, { instructions: OPERATING_BRIEF });
49
49
  const ok = (obj) => ({
50
50
  content: [{ type: "text", text: JSON.stringify(obj, null, 2) }],
51
51
  });
@@ -180,7 +180,7 @@ server.registerTool("get_crestron_time", {
180
180
  server.registerTool("get_crestron_processor_info", {
181
181
  description: "Describe the processor itself: model, firmware, hostname, IP address, MAC, the running " +
182
182
  "program (slot, name, program comments), uptime, the processor's clock, time zone and " +
183
- "location, the MCP for Crestron modules version, and how many devices, rooms and schedules " +
183
+ "location, the RoomTalk modules version, and how many devices, rooms and schedules " +
184
184
  "it holds. Use it for questions about the system rather than a device, and to explain " +
185
185
  "sunrise/sunset times (a location_warning means the location was never set).",
186
186
  }, async () => {
@@ -630,10 +630,10 @@ server.registerTool("start_crestron_trial", {
630
630
  async function main() {
631
631
  const transport = new StdioServerTransport();
632
632
  await server.connect(transport);
633
- console.error(`mcp-for-crestron: ready (target ${cfg.host}:${cfg.port}, ` +
633
+ console.error(`roomtalk-for-crestron: ready (target ${cfg.host}:${cfg.port}, ` +
634
634
  `${cfg.key ? "mode 2 key" : cfg.auth ? "mode 1 password" : "open"}${cfg.tls ? " + TLS" : ""})`);
635
635
  }
636
636
  main().catch((e) => {
637
- console.error("mcp-for-crestron: fatal", e);
637
+ console.error("roomtalk-for-crestron: fatal", e);
638
638
  process.exit(1);
639
639
  });
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "manifest_version": "0.2",
3
- "name": "mcp-for-crestron",
4
- "display_name": "MCP for Crestron",
5
- "version": "1.20.0",
3
+ "name": "roomtalk-for-crestron",
4
+ "display_name": "RoomTalk for Crestron",
5
+ "version": "1.21.0",
6
6
  "icon": "icon.png",
7
7
  "description": "Query and control a Crestron 4-Series AV system in natural language.",
8
- "long_description": "Connects Claude to a Crestron 4-Series processor running the MCP for Crestron modules. Lets you discover rooms and devices, read and set lighting, AV, HVAC and shades, and smoothly ramp analog levels, all in plain English. Talks to the processor over the MCP for Crestron text protocol, with optional password (mode 1) or secure-key + TLS (mode 2) authentication. Crestron is a registered trademark of Crestron Electronics, Inc.; MCP for Crestron is a product of Solution AV Automation, not affiliated with or endorsed by Crestron.",
8
+ "long_description": "Connects Claude to a Crestron 4-Series processor running the RoomTalk for Crestron modules (or the earlier MCP for Crestron modules). Lets you discover rooms and devices, read and set lighting, AV, HVAC and shades, and smoothly ramp analog levels, all in plain English. Talks to the processor over the MCP for Crestron text protocol, with optional password (mode 1) or secure-key + TLS (mode 2) authentication. Crestron is a registered trademark of Crestron Electronics, Inc.; MCP for Crestron is a product of Solution AV Automation, not affiliated with or endorsed by Crestron.",
9
9
  "author": {
10
10
  "name": "Solution AV Automation"
11
11
  },
@@ -61,7 +61,7 @@
61
61
  "port": {
62
62
  "type": "number",
63
63
  "title": "Port",
64
- "description": "TCP port the MCP for Crestron server listens on.",
64
+ "description": "Use 50794 unless port forwarding has been set up.",
65
65
  "default": 50794,
66
66
  "required": false
67
67
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "roomtalk-for-crestron",
3
- "version": "1.20.0",
3
+ "version": "1.21.0",
4
4
  "description": "RoomTalk for Crestron (formerly MCP for Crestron): talk to a Crestron 4-Series AV system through Claude in natural language. Not affiliated with Crestron.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -22,16 +22,16 @@
22
22
  "build": "tsc",
23
23
  "start": "node dist/index.js",
24
24
  "bundle": "bun build src/index.ts --target=node --format=esm --outfile mcpb/server/index.mjs",
25
- "mcpb": "npm run bundle && mcpb pack mcpb mcp-for-crestron.mcpb",
25
+ "mcpb": "npm run bundle && mcpb pack mcpb roomtalk-for-crestron.mcpb",
26
26
  "prepublishOnly": "npm run build"
27
27
  },
28
28
  "repository": {
29
29
  "type": "git",
30
- "url": "git+https://github.com/SolutionAVAutomation/mcp-for-crestron-client.git"
30
+ "url": "git+https://github.com/SolutionAVAutomation/roomtalk-for-crestron-client.git"
31
31
  },
32
32
  "homepage": "https://solutionav.com.au/crestron-mcp/",
33
33
  "bugs": {
34
- "url": "https://github.com/SolutionAVAutomation/mcp-for-crestron-client/issues"
34
+ "url": "https://github.com/SolutionAVAutomation/roomtalk-for-crestron-client/issues"
35
35
  },
36
36
  "keywords": [
37
37
  "mcp",