All servers / Developer / Skyelight
Skyelight
Website feedback for your coding agent: comments pinned to the exact element, with its code.
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://app.skyelight.ai/mcp · Registry name: ai.skyelight/mcp
Score 83 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 19 / 20 | |
| Inputs explained | 14 / 15 | |
| Speed | 0 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (0.6 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: skyelight 1.2.0
- Tools offered: 19 · Parameters with a plain description: 61 of 67
- One safe, read-only test call to
list_workspaces: failed (first call 0.1 seconds) - Official registry entry last updated: 2026-11-19
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
list_workspacesno parametersWorkspaces you can reach, with the role you hold in each, and who you are. Use when you do not know what exists yet, to find which workspace a project belongs to, or to learn your own user id.
list_projects1 of 1 parameter describedProjects you can reach, newest activity first, across every workspace unless one is named. Start here when no project is bound — `list_items` needs a project id and this is where one comes from.
create_project2 of 2 parameters describedCreate a project: where one site or app's feedback lives. Use when the person has none yet (list_workspaces shows 0 projects) or asks for another. Ask what the site or app is called if you do not know. The answer says how they leave their first feedback. The same name again returns the project already made.
list_items7 of 7 parameters describedList feedback items (bugs, ideas, comments) people left on a Skyelight project. Returns a summary of the project plus matching items. Start here to see what is outstanding. An item's hand-off (investigate, plan, fix) is set by the team and binding: on investigate or plan, reply on the thread and change no code.
search_items2 of 4 parameters describedFind items whose thread mentions some text. Searches replies as well as the original message, so an item someone already diagnosed in a reply still turns up.
post_update4 of 4 parameters describedReport back on an item: what you found, what you changed, a link to the PR. Posts as a reply on the thread the feedback was left on, so the person who reported it sees the answer where they asked. Use this when you finish work on an item, and when you get stuck.
create_item6 of 7 parameters describedOpen a new thread on a page, as the person whose connection you are using. Only available on a person's own connection — an agent reporting what it found or changed uses post_update on the thread it was working, so the answer lands where the question was asked.
publish_review_link8 of 8 parameters describedShare something with Skyelight for review, and get a link people can pin feedback on. Two ways: - code: one file Skyelight hosts at its own link with the review badge on it. A whole HTML page, or one React component with an export default (Tailwind classes and npm imports work; local imports such as @/components do not). For Claude prototypes, v0 snippets and single pages. Publishing again with the same prototypeId, or the same name in the same project, makes a new version at the same link. - url: an app already deployed (a Lovable, v0, Bolt or Vercel project: anything with more than one file). Adds its address to the project's Review Links and returns a script tag to add to the app's <head> (index.html, or the root layout); add it and redeploy. Owners and admins. Returns the share link and the project link; give both to the person. A hosted link is public to anyone who has it.
list_members2 of 2 parameters describedThe people in a workspace: name, email, role and id. Call it when you are asked to tell, ask or hand something to someone by name, then pass their name or id to assign, or in mentions on create_item or post_update.
assign2 of 2 parameters describedHand an item to a person, who is notified the way an assignment in the app notifies them. Pass null as the assignee to unassign it. Only owners, admins and collaborators can assign; a resolved item has to be reopened first.
set_status1 of 2 parameters describedMove an item to open, deferred or resolved. Use it to close the loop after you have fixed something and said so — post_update first, so the person who reported it reads what changed, then set_status. "deferred" is for work that is real but not now.
get_item1 of 1 parameter describedEverything needed to work one item: the whole thread in order, the page and URL it is on, the anchor identifying the element the person pointed at, and the pictures — what the page looked like when it was pinned, plus anything people attached — returned as images you can look at rather than links you cannot.
project_review3 of 3 parameters describedEverything needed to write an accurate project review or hand-off document: the shape of the work, every resolved thread and how it ended, what was deferred and why, what is still open, and the longest conversations quoted in full, which is where decisions were made. Every entry carries its item id, so each claim in your document can be traced back to its thread. Quote; do not invent outcomes the threads do not state.
whats_new2 of 2 parameters describedWhat changed on a project since you last looked: new threads, new replies grouped by thread, what was resolved or deferred, and what was assigned to you or mentioned you. Use when the user asks what has changed on a project since they last checked. Without `since` it reads from their bookmark and moves it forward; with `since` it reads that window and leaves the bookmark alone.
find_by_source4 of 6 parameters describedFeedback by the code that rendered it, from the file and line the Skyelight build plugin stamps on each element. Pass a file (a path or just its name) or a component to see every thread about it before you edit it; pass neither to get the hot spots, every stamped file ranked by outstanding feedback.
find_similar7 of 7 parameters describedHas this already been reported? Pass the text you are about to report (and the page, if you know it) before create_item, or an itemId to find what an existing thread duplicates. Returns likely matches with why each matched: shared words, same page, same element, same source file. If two are the same problem, merge_items folds one into the other.
merge_items2 of 2 parameters describedFold duplicate items into one, the way merging works in the app: the duplicates leave the list and count as extra reports on the item they were merged into. Use it only when find_similar and the threads themselves show they are the same problem. Owners, admins and collaborators can merge.
decision_log4 of 4 parameters describedThe decisions a project made in its threads, quoted: every thread resolved or deferred after a discussion, with the conversation, plus types people corrected and where outcomes keep recurring. Also returns the project's existing rules, so you can tell what is new. Use it to write a decision log, or to find rules worth keeping with save_rule.
save_rule3 of 3 parameters describedKeep a rule the team agreed on ("sentence case in every button", "the brand gray stays, do not raise contrast bugs on it") in the project's context, under Rules learned. The classifier reads that context, and every agent reads it through decision_log, so it shapes future threads. Cite the threads it came from. Workspace owners and admins only; confirm with the person before saving.
Tested by ConnectATD. Spotted a mistake? Tell us.