@skyelight/mcp 0.7.0 → 0.7.2

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/CHANGELOG.md CHANGED
@@ -11,7 +11,24 @@ keeps working. A **patch** is a fix or a wording change. A **major** would be
11
11
  removing a tool or an argument, or changing what an existing field means, and
12
12
  there has not been one.
13
13
 
14
- ## 0.7.0 — unreleased
14
+ ## 0.7.2 — 2026-10-08
15
+
16
+ ### Changed
17
+
18
+ - **Source on GitHub.** The package's source is published at
19
+ [github.com/plastrlab/skyelight-mcp](https://github.com/plastrlab/skyelight-mcp),
20
+ and `package.json` names it as the repository, so npm links to it. The
21
+ license is unchanged: free to install and run with a Skyelight account
22
+ (see `LICENSE`). No change to the tools.
23
+
24
+ ## 0.7.1 — 2026-10-05
25
+
26
+ ### Changed
27
+
28
+ - **Docs.** The README lists `publish_review_link` and says what the MCP
29
+ does on Free. No change to the tools.
30
+
31
+ ## 0.7.0 — 2026-10-05
15
32
 
16
33
  ### Changed
17
34
 
package/README.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # @skyelight/mcp
2
2
 
3
+ [npm](https://www.npmjs.com/package/@skyelight/mcp) ·
4
+ [source](https://github.com/plastrlab/skyelight-mcp) ·
5
+ [docs](https://skyelight.ai/docs/mcp)
6
+
3
7
  An MCP server that lets a coding agent read the feedback people left on your
4
8
  running app — the thread, the page, and the element they were pointing at —
5
9
  and report back on it when the work is done.
@@ -8,7 +12,7 @@ Full guide: [skyelight.ai/docs/mcp](https://skyelight.ai/docs/mcp). The REST
8
12
  API behind the local server is documented at
9
13
  [skyelight.ai/docs/api](https://skyelight.ai/docs/api).
10
14
 
11
- Two ways to connect, with the same seventeen tools either way:
15
+ Two ways to connect, with the same eighteen tools either way:
12
16
 
13
17
  - **Remote, with OAuth** — the default. Your agent talks to Skyelight over
14
18
  HTTP and you sign in once in the browser. Nothing is pasted and no key is
@@ -18,8 +22,10 @@ Two ways to connect, with the same seventeen tools either way:
18
22
  browser sign-in is not an option.
19
23
 
20
24
  Coding agents need a paid seat (owner, admin or collaborator) on a Pro plan or
21
- above. A reviewer seat reads and comments in the web app but does not carry
22
- agent tools.
25
+ above. On Free, the same seat connects too and can publish to Skyelight
26
+ (`publish_review_link`, one hosted prototype); reading feedback with an agent
27
+ is on Pro. A reviewer seat reads and comments in the web app but does not
28
+ carry agent tools.
23
29
 
24
30
  ## The short way
25
31
 
@@ -101,25 +107,41 @@ agent calls `list_projects` first rather than guess.
101
107
 
102
108
  ## Tools
103
109
 
104
- | Tool | What it is for |
105
- | ----------------- | ----------------------------------------------------------------------- |
106
- | `list_workspaces` | Which workspaces this credential can reach, and who you are. |
107
- | `list_projects` | The projects inside them, with the ids the other tools take. |
108
- | `list_items` | What is outstanding. Filter by page, type, status, assignee. |
109
- | `search_items` | Find items whose thread mentions some text, replies included. |
110
- | `get_item` | Everything needed to work one item: thread, page, anchor, code, images. |
111
- | `post_update` | Report back on the thread the feedback came from. |
112
- | `create_item` | Raise a new item — an audit finding, something you noticed. |
113
- | `set_status` | Move an item to open, deferred or resolved. |
114
- | `list_members` | Who is in the workspace, so you can name an assignee or a mention. |
115
- | `assign` | Hand an item to a person, or unassign it. |
116
- | `whats_new` | What changed since you last looked, from your own bookmark. |
117
- | `project_review` | Where a project landed, for a wrap-up or hand-off document. |
118
- | `decision_log` | What the team decided in its threads, quoted, and its current rules. |
119
- | `save_rule` | Keep an agreed rule in the project context (owners and admins). |
120
- | `find_by_source` | Feedback on a file or component before you edit it, or the hot spots. |
121
- | `find_similar` | Check for an existing report before creating one. |
122
- | `merge_items` | Fold duplicate items into one. |
110
+ | Tool | What it is for |
111
+ | --------------------- | ------------------------------------------------------------------------------------ |
112
+ | `list_workspaces` | Which workspaces this credential can reach, and who you are. |
113
+ | `list_projects` | The projects inside them, with the ids the other tools take. |
114
+ | `list_items` | What is outstanding. Filter by page, type, status, assignee. |
115
+ | `search_items` | Find items whose thread mentions some text, replies included. |
116
+ | `get_item` | Everything needed to work one item: thread, page, anchor, code, images. |
117
+ | `post_update` | Report back on the thread the feedback came from. |
118
+ | `create_item` | Raise a new item — an audit finding, something you noticed. |
119
+ | `set_status` | Move an item to open, deferred or resolved. |
120
+ | `list_members` | Who is in the workspace, so you can name an assignee or a mention. |
121
+ | `assign` | Hand an item to a person, or unassign it. |
122
+ | `whats_new` | What changed since you last looked, from your own bookmark. |
123
+ | `project_review` | Where a project landed, for a wrap-up or hand-off document. |
124
+ | `decision_log` | What the team decided in its threads, quoted, and its current rules. |
125
+ | `save_rule` | Keep an agreed rule in the project context (owners and admins). |
126
+ | `find_by_source` | Feedback on a file or component before you edit it, or the hot spots. |
127
+ | `find_similar` | Check for an existing report before creating one. |
128
+ | `merge_items` | Fold duplicate items into one. |
129
+ | `publish_review_link` | Share something for review: code for Skyelight to host, or a deployed app's address. |
130
+
131
+ **Publishing for review.** `publish_review_link` takes one of two things:
132
+
133
+ - `code`: one HTML page, or one React component with an export default (a
134
+ Claude prototype, a v0 snippet). Skyelight hosts it at its own link on
135
+ `skyelight.page` with the review badge on it, in a project you name or a new
136
+ one. Publishing again makes a new version at the same link.
137
+ - `url`: an app already deployed, such as a Lovable, v0 or Bolt project on
138
+ `*.lovable.app` or `*.vercel.app`. The address goes on the project's Review
139
+ Links, and the answer carries a script tag for the app's `<head>` and the
140
+ review link to share (the address with `?skyelight=1`).
141
+
142
+ Code that imports the rest of its app is not hosted; the answer says to send
143
+ the app's `url` instead. It answers to `publish_prototype` too, its name
144
+ before 0.7.0.
123
145
 
124
146
  `list_items` leads with a summary — totals, breakdown by type and by page — so
125
147
  an agent can tell you the shape of the work before pulling any of it. Rows are
@@ -205,10 +227,14 @@ The server enforces nothing; the API does. The agent can do what your account
205
227
  can do in that workspace, and nothing more:
206
228
 
207
229
  - Agent tools need a **paid seat** (owner, admin or collaborator) in an
208
- organization on **Pro or above**. A reviewer seat, or a Free plan, is
209
- refused with the reason — the workspace is listed and marked rather than
210
- hidden, so you are told which gate closed instead of being told it does not
211
- exist.
230
+ organization on **Pro or above**. A reviewer seat is refused with the
231
+ reason — the workspace is listed and marked rather than hidden, so you are
232
+ told which gate closed instead of being told it does not exist.
233
+ - **On Free**, a paid seat connects for publishing: `list_workspaces`,
234
+ `list_projects` and `publish_review_link` (one hosted prototype). The
235
+ reading tools answer with how much feedback is waiting and that reading it
236
+ is on Pro; the rest name the plan.
237
+ - Adding a deployed app's address to Review Links is for owners and admins.
212
238
  - Owners, admins and collaborators read, reply, raise items and change any
213
239
  thread's status.
214
240
  - A token only reaches workspaces in the organization it was created in.
package/package.json CHANGED
@@ -1,7 +1,8 @@
1
1
  {
2
2
  "name": "@skyelight/mcp",
3
- "version": "0.7.0",
3
+ "version": "0.7.2",
4
4
  "description": "MCP server for Skyelight — read feedback items from your project as an agent",
5
+ "mcpName": "io.github.plastrlab/skyelight-mcp",
5
6
  "type": "module",
6
7
  "bin": {
7
8
  "skyelight-mcp": "./src/index.js"
@@ -25,9 +26,17 @@
25
26
  "skyelight",
26
27
  "feedback"
27
28
  ],
28
- "license": "UNLICENSED",
29
- "homepage": "https://skyelight.ai",
29
+ "license": "SEE LICENSE IN LICENSE",
30
+ "homepage": "https://github.com/plastrlab/skyelight-mcp#readme",
30
31
  "publishConfig": {
31
32
  "access": "public"
32
- }
33
+ },
34
+ "repository": {
35
+ "type": "git",
36
+ "url": "git+https://github.com/plastrlab/skyelight-mcp.git"
37
+ },
38
+ "bugs": {
39
+ "url": "https://github.com/plastrlab/skyelight-mcp/issues"
40
+ },
41
+ "author": "Plastr Lab (https://skyelight.ai)"
33
42
  }
package/src/version.js CHANGED
@@ -12,4 +12,4 @@
12
12
  * filesystem there. `test/server.test.js` asserts the two agree, so the pair
13
13
  * cannot drift again without a test going red.
14
14
  */
15
- export const VERSION = "0.7.0";
15
+ export const VERSION = "0.7.2";