Connect your agent
This page shows how to connect a coding agent or assistant to the Skyelight MCP server. In Claude Code, install the plugin, in ChatGPT, add the plugin, in claude.ai, add the connector, and in Gemini CLI, install the extension. Most other agents connect with one command and a browser sign-in.
You need an owner, admin or collaborator role in a workspace. The agent gets every tool on every plan. On the Free plan it gets 25 agent threads a month, and pins and threads are unlimited. See Requirements and Plans and billing.
Claude Code: install the plugin
Skyelight is in Claude Code’s plugin directory. The plugin connects Claude Code to the remote server and adds a skill for working through feedback, plus two commands.
If you added Skyelight to Claude Code before, with the installer or
claude mcp add, remove that copy so Claude doesn’t see two servers:
claude mcp remove skyelight -s user.
ChatGPT: add the plugin
Skyelight is in ChatGPT’s plugin directory, so there is no server address to paste.
Open Skyelight in ChatGPT
Open Skyelight in ChatGPT , or search for Skyelight in ChatGPT’s plugins.
If you added Skyelight to ChatGPT before as a custom connector, remove that copy so ChatGPT doesn’t see two.
claude.ai: add the connector
Skyelight is in Claude’s connector directory. The connector works in claude.ai and in the Claude desktop and mobile apps.
Open Skyelight in Claude
Open Skyelight in Claude , or search for Skyelight in Claude’s connectors.
If you added Skyelight to claude.ai before as a custom connector, remove that copy so Claude doesn’t see two.
Gemini CLI: install the extension
Skyelight is a Gemini CLI extension. It connects Gemini CLI to the remote server and adds the same skill and commands as the Claude Code plugin.
gemini extensions update skyelight brings in a new version.
Install with one command
Run the installer
npx @skyelight/mcp initThe installer finds the coding agents on your machine and shows the change it will make to each one. It writes nothing until you confirm. It registers the remote server and leaves sign-in to OAuth, so no token is written to disk.
It supports Claude Code, Cursor, Grok, Codex, Gemini CLI and Windsurf. If it finds more than one, it asks which to set up.
Installer options
| Command | What it does |
|---|---|
npx @skyelight/mcp init --client <id> | Sets up the named agent without asking which. <id> is claude, cursor, grok, codex, gemini or windsurf |
npx @skyelight/mcp init --client all | Sets up every agent it finds |
npx @skyelight/mcp init --yes | Writes the change without asking for confirmation |
npx @skyelight/mcp remove | Removes Skyelight from every supported agent, asking before each change |
From the app
Account Settings Coding Agents in the web app shows the installer command and a config snippet for each client. On the Free plan, the page also shows how many threads your agent has worked this month, out of 25. The snippets include the server URL and the OAuth client ID. Use them to edit a client’s config yourself. The snippets below match that page.
The server URL is:
https://app.skyelight.ai/mcpRun:
claude mcp add -s user --transport http skyelight \
--client-id RbF6Ga0l6S49Qsvu \
--callback-port 54545 \
https://app.skyelight.ai/mcpFrom the MCP Registry
Skyelight is listed in the official MCP Registry
as ai.skyelight/mcp. Agents and directories that read the
registry can add it from there. Choose the remote server,
https://app.skyelight.ai/mcp, and your agent opens Skyelight so you can sign
in. If you choose the @skyelight/mcp package instead, it needs a
personal token.
With a token
Use a personal token when you can’t sign in through a browser, for example on
a remote machine. The @skyelight/mcp package runs on your machine as a stdio
server and sends the token with each request.
Add the server to your client
{ "mcpServers": { "skyelight": { "command": "npx", "args": ["-y", "@skyelight/mcp"], "env": { "SKYELIGHT_API_URL": "https://app.skyelight.ai", "SKYELIGHT_API_TOKEN": "sky_..." } } } }In Claude Code, you can add the server from the command line instead:
claude mcp add skyelight \ --env SKYELIGHT_API_URL=https://app.skyelight.ai \ --env SKYELIGHT_API_TOKEN=sky_... \ -- npx -y @skyelight/mcpSet
SKYELIGHT_API_URLto the app’s address without/mcp.
About tokens
- A token acts as you, with your access. Keep it out of source control.
- A token belongs to the organization you created it in and only reaches that organization’s workspaces.
- You can hold up to 10 active tokens per organization.
- Skyelight revokes your tokens for an organization when you stop holding a paid seat there, for example when you become a reviewer in every workspace or are removed. A later promotion doesn’t restore them. Create a new token.
- You can revoke a token at any time on the API Keys page.
API authentication covers tokens and the API that the local server calls.
Where the local server looks for credentials
The local server checks these locations in order. For each value, it uses the first one it finds:
SKYELIGHT_API_TOKENandSKYELIGHT_API_URLin the environment.env.local, then.env, in the working directory~/.skyelight/credentials, as{"apiUrl": "...", "token": "sky_..."}
Binding a repository to a project
With the local server, add a .skyelight.json file to the root of your
repository. Tools then use that project when no projectId is given:
// .skyelight.json
{ "projectId": "j57abc...", "projectName": "Checkout rebuild" }The agent can find the project ID with list_projects. The remote server
doesn’t read this file. With the remote server, the agent asks for a project or
calls list_projects first.
For sign-in errors and refusals, see Troubleshooting.