Use Skyelight with Cursor
Skyelight’s MCP server gives Cursor’s agent your team’s feedback: every open thread, the page and element it’s pinned to and, with Skyelight Build, the source file and line behind it. The agent can fix a thread in the editor and reply on it when it’s done, so the person who left the feedback sees the answer where they asked.
Setup takes one command and a browser sign-in.
Connect Cursor
Check the tools are on
Open Cursor’s settings and find the MCP section. Skyelight should be listed with its tools enabled. If it shows an error, see Troubleshooting.
Or add it by hand
Add the server to ~/.cursor/mcp.json to use it in every project, or to
.cursor/mcp.json in a repository to share it with everyone who opens that
repository:
// ~/.cursor/mcp.json
{
"mcpServers": {
"skyelight": { "url": "https://app.skyelight.ai/mcp" }
}
}The URL holds no secret, so the project file is safe to commit. Each person signs in with their own Skyelight account, and the agent only sees what that person can see.
What to ask Cursor’s agent
Use the agent, not a quick edit, so it can call tools. Some prompts that work well:
| Ask | What happens |
|---|---|
| ”What’s open on my Skyelight project?” | Lists open threads with the page, the element and, with Skyelight Build, the file and line |
| ”Work through my Skyelight inbox.” | Picks up the threads assigned to you and does the task set on each: investigate, plan or fix |
| ”Fix the heading thread on the pricing page.” | Opens the file behind the element, makes the change and replies on the thread |
| ”Is there feedback on this file?” | Checks for threads on the file before it edits it |
| ”What has the team decided on this project?” | Reads the decision log, so the change follows what was agreed |
The agent replies on the thread as you, with a note that it came from Cursor. It leaves the thread open, so a person checks the change before it’s resolved. See Working with an agent for longer flows.
Plans
On the Free plan Cursor connects and can list your workspaces and projects and publish one hosted prototype. Reading and replying to feedback is on Pro and Team. See Plans and billing.