@skyelight/mcp 0.7.0 → 0.7.1
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 +8 -1
- package/README.md +48 -26
- package/package.json +1 -1
- package/src/version.js +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -11,7 +11,14 @@ 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.
|
|
14
|
+
## 0.7.1 — unreleased
|
|
15
|
+
|
|
16
|
+
### Changed
|
|
17
|
+
|
|
18
|
+
- **Docs.** The README lists `publish_review_link` and says what the MCP
|
|
19
|
+
does on Free. No change to the tools.
|
|
20
|
+
|
|
21
|
+
## 0.7.0 — 2026-10-05
|
|
15
22
|
|
|
16
23
|
### Changed
|
|
17
24
|
|
package/README.md
CHANGED
|
@@ -8,7 +8,7 @@ Full guide: [skyelight.ai/docs/mcp](https://skyelight.ai/docs/mcp). The REST
|
|
|
8
8
|
API behind the local server is documented at
|
|
9
9
|
[skyelight.ai/docs/api](https://skyelight.ai/docs/api).
|
|
10
10
|
|
|
11
|
-
Two ways to connect, with the same
|
|
11
|
+
Two ways to connect, with the same eighteen tools either way:
|
|
12
12
|
|
|
13
13
|
- **Remote, with OAuth** — the default. Your agent talks to Skyelight over
|
|
14
14
|
HTTP and you sign in once in the browser. Nothing is pasted and no key is
|
|
@@ -18,8 +18,10 @@ Two ways to connect, with the same seventeen tools either way:
|
|
|
18
18
|
browser sign-in is not an option.
|
|
19
19
|
|
|
20
20
|
Coding agents need a paid seat (owner, admin or collaborator) on a Pro plan or
|
|
21
|
-
above.
|
|
22
|
-
agent
|
|
21
|
+
above. On Free, the same seat connects too and can publish to Skyelight
|
|
22
|
+
(`publish_review_link`, one hosted prototype); reading feedback with an agent
|
|
23
|
+
is on Pro. A reviewer seat reads and comments in the web app but does not
|
|
24
|
+
carry agent tools.
|
|
23
25
|
|
|
24
26
|
## The short way
|
|
25
27
|
|
|
@@ -101,25 +103,41 @@ agent calls `list_projects` first rather than guess.
|
|
|
101
103
|
|
|
102
104
|
## Tools
|
|
103
105
|
|
|
104
|
-
| Tool
|
|
105
|
-
|
|
|
106
|
-
| `list_workspaces`
|
|
107
|
-
| `list_projects`
|
|
108
|
-
| `list_items`
|
|
109
|
-
| `search_items`
|
|
110
|
-
| `get_item`
|
|
111
|
-
| `post_update`
|
|
112
|
-
| `create_item`
|
|
113
|
-
| `set_status`
|
|
114
|
-
| `list_members`
|
|
115
|
-
| `assign`
|
|
116
|
-
| `whats_new`
|
|
117
|
-
| `project_review`
|
|
118
|
-
| `decision_log`
|
|
119
|
-
| `save_rule`
|
|
120
|
-
| `find_by_source`
|
|
121
|
-
| `find_similar`
|
|
122
|
-
| `merge_items`
|
|
106
|
+
| Tool | What it is for |
|
|
107
|
+
| --------------------- | ------------------------------------------------------------------------------------ |
|
|
108
|
+
| `list_workspaces` | Which workspaces this credential can reach, and who you are. |
|
|
109
|
+
| `list_projects` | The projects inside them, with the ids the other tools take. |
|
|
110
|
+
| `list_items` | What is outstanding. Filter by page, type, status, assignee. |
|
|
111
|
+
| `search_items` | Find items whose thread mentions some text, replies included. |
|
|
112
|
+
| `get_item` | Everything needed to work one item: thread, page, anchor, code, images. |
|
|
113
|
+
| `post_update` | Report back on the thread the feedback came from. |
|
|
114
|
+
| `create_item` | Raise a new item — an audit finding, something you noticed. |
|
|
115
|
+
| `set_status` | Move an item to open, deferred or resolved. |
|
|
116
|
+
| `list_members` | Who is in the workspace, so you can name an assignee or a mention. |
|
|
117
|
+
| `assign` | Hand an item to a person, or unassign it. |
|
|
118
|
+
| `whats_new` | What changed since you last looked, from your own bookmark. |
|
|
119
|
+
| `project_review` | Where a project landed, for a wrap-up or hand-off document. |
|
|
120
|
+
| `decision_log` | What the team decided in its threads, quoted, and its current rules. |
|
|
121
|
+
| `save_rule` | Keep an agreed rule in the project context (owners and admins). |
|
|
122
|
+
| `find_by_source` | Feedback on a file or component before you edit it, or the hot spots. |
|
|
123
|
+
| `find_similar` | Check for an existing report before creating one. |
|
|
124
|
+
| `merge_items` | Fold duplicate items into one. |
|
|
125
|
+
| `publish_review_link` | Share something for review: code for Skyelight to host, or a deployed app's address. |
|
|
126
|
+
|
|
127
|
+
**Publishing for review.** `publish_review_link` takes one of two things:
|
|
128
|
+
|
|
129
|
+
- `code`: one HTML page, or one React component with an export default (a
|
|
130
|
+
Claude prototype, a v0 snippet). Skyelight hosts it at its own link on
|
|
131
|
+
`skyelight.page` with the review badge on it, in a project you name or a new
|
|
132
|
+
one. Publishing again makes a new version at the same link.
|
|
133
|
+
- `url`: an app already deployed, such as a Lovable, v0 or Bolt project on
|
|
134
|
+
`*.lovable.app` or `*.vercel.app`. The address goes on the project's Review
|
|
135
|
+
Links, and the answer carries a script tag for the app's `<head>` and the
|
|
136
|
+
review link to share (the address with `?skyelight=1`).
|
|
137
|
+
|
|
138
|
+
Code that imports the rest of its app is not hosted; the answer says to send
|
|
139
|
+
the app's `url` instead. It answers to `publish_prototype` too, its name
|
|
140
|
+
before 0.7.0.
|
|
123
141
|
|
|
124
142
|
`list_items` leads with a summary — totals, breakdown by type and by page — so
|
|
125
143
|
an agent can tell you the shape of the work before pulling any of it. Rows are
|
|
@@ -205,10 +223,14 @@ The server enforces nothing; the API does. The agent can do what your account
|
|
|
205
223
|
can do in that workspace, and nothing more:
|
|
206
224
|
|
|
207
225
|
- Agent tools need a **paid seat** (owner, admin or collaborator) in an
|
|
208
|
-
organization on **Pro or above**. A reviewer seat
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
226
|
+
organization on **Pro or above**. A reviewer seat is refused with the
|
|
227
|
+
reason — the workspace is listed and marked rather than hidden, so you are
|
|
228
|
+
told which gate closed instead of being told it does not exist.
|
|
229
|
+
- **On Free**, a paid seat connects for publishing: `list_workspaces`,
|
|
230
|
+
`list_projects` and `publish_review_link` (one hosted prototype). The
|
|
231
|
+
reading tools answer with how much feedback is waiting and that reading it
|
|
232
|
+
is on Pro; the rest name the plan.
|
|
233
|
+
- Adding a deployed app's address to Review Links is for owners and admins.
|
|
212
234
|
- Owners, admins and collaborators read, reply, raise items and change any
|
|
213
235
|
thread's status.
|
|
214
236
|
- A token only reaches workspaces in the organization it was created in.
|
package/package.json
CHANGED
package/src/version.js
CHANGED