Connect AI apps
If you build sites with an AI app next to you, it can read the comments your clients and teammates leave, see where each one is pinned, change the code they are about, then reply and resolve the ones it fixed.
SharedLayers is an MCP server for this: a connector any app that supports MCP can add, at one address:
https://sharedlayers.com/mcp
Every app signs in the same way. Your browser opens on SharedLayers, you sign in if you are not already, and a screen names the app, says what it will see and where it sends you back to, and asks you to allow it. Nothing is shared until you do. The same steps are under Connect AI in the dashboard, with copy buttons.
Pick your app
- Claude Code
- Claude, web and desktop
- Claude for Team or Enterprise
- ChatGPT
- Codex
- Cursor
- Gemini CLI
- VS Code
- Any other MCP app
Want comments to reach your coding AI the moment they are written? That is what AI layers are for: a private layer on an app on your own computer, where each comment goes straight to Claude Code, Codex, GitHub Copilot or Cursor, which changes the code and answers. This page is about the connector, which works with every layer, on every site.
Claude Code
- In the folder of the site you are working on, run:
To have it in every folder rather than just this one, addclaude mcp add --transport http sharedlayers https://sharedlayers.com/mcp--scope userafteradd. - Start a new Claude Code session there. A session that was already open does not see servers added after it started.
- Type
/mcp, choosesharedlayers, then Authenticate. - In the browser, sign in to SharedLayers and select Allow. The browser goes back to Claude Code on its own.
To have Claude go through the open comments, fix them and resolve the ones it fixed in one go, add the fix-comments skill once, for every project:
mkdir -p ~/.claude/skills/fix-comments && curl -fsSL https://sharedlayers.com/skills/fix-comments/SKILL.md -o ~/.claude/skills/fix-comments/SKILL.md
Then type /fix-comments, or /fix-comments acme.com for one site. The connector also offers the same steps as its fix_comments prompt, in apps that list a server's prompts.
Claude on the web and desktop
On a Free, Pro or Max plan you add the connector to your own account (the Free plan allows one custom connector):
- In Claude, go to Customize > Connectors and select Add custom connector.
- Enter the address
https://sharedlayers.com/mcp. If the dialog asks how Claude identifies itself (OAuth client), choose Register automatically. Leave the client ID and secret empty. - Select Add, then Connect, then sign in to SharedLayers and select Allow.
- In a chat, open the + menu, then Connectors, and check that SharedLayers is on.
Claude for Team or Enterprise
In an organization only an Owner can add a custom connector (on Enterprise, also anyone whose role can manage the organization's libraries). They add it once, for everyone. Then each person connects with their own SharedLayers account and sees only the comments that account can see. Connect AI in the dashboard has a note you can copy and send to your Owner.
The Owner, once:
- Go to Organization settings > Connectors, select Add, then Custom. If asked for the type, choose Web.
- Enter the address
https://sharedlayers.com/mcp. For OAuth client, choose Register automatically, and leave the client ID and secret empty. - Select Add.
Then everyone else:
- Go to Customize > Connectors and find SharedLayers, with the Custom label.
- Select Connect, sign in to SharedLayers with your own account, and select Allow.
ChatGPT and Codex
ChatGPT
- Go to Plugins, select +, then Add custom MCP server.
- Name it SharedLayers and enter the address
https://sharedlayers.com/mcp. For authentication, choose OAuth. Read the warning and continue. - Create it, then sign in to SharedLayers and select Allow.
- In a chat, type
@and pick SharedLayers.
Whether you can add a custom MCP server depends on your ChatGPT plan, and in a workspace on what its admin allows.
Codex
Run these two commands. The second opens your browser on SharedLayers; select Allow. The Codex CLI, app and IDE extension share this setup, so it is done once for all three.
codex mcp add sharedlayers --url https://sharedlayers.com/mcp
codex mcp login sharedlayers
Cursor
Add to Cursor under Connect AI in the dashboard opens Cursor and adds the server. Or add it yourself, to ~/.cursor/mcp.json for every project or to .cursor/mcp.json in one:
{
"mcpServers": {
"sharedlayers": { "url": "https://sharedlayers.com/mcp" }
}
}
When Cursor asks you to sign in to sharedlayers, sign in to SharedLayers and select Allow. Its MCP servers are listed, and can be switched off, under Customize.
Gemini CLI
- In the folder of the site you are working on, run:
To have it in every folder rather than just this one, addgemini mcp add --transport http sharedlayers https://sharedlayers.com/mcp--scope userafteradd. - Start Gemini CLI there and type
/mcp auth sharedlayers. - In the browser, sign in to SharedLayers and select Allow.
VS Code and other apps
Any app that can add a remote MCP server (Streamable HTTP) can use the same address, and signs in the same way. In VS Code, Add to VS Code under Connect AI adds it to your profile; or add it to .vscode/mcp.json in the project:
{
"servers": {
"sharedlayers": { "type": "http", "url": "https://sharedlayers.com/mcp" }
}
}
An app that can only start local servers can reach it through mcp-remote, which opens the same sign-in in your browser. Give the app this as the server's command:
npx -y mcp-remote https://sharedlayers.com/mcp
What to ask
- What is still open on acme.com?
- Fix the critical comments on the pricing page and resolve them.
- Read the replies on the hero comment and tell me what they settled on.
When it has made a change, it resolves the comment with a short reply saying what changed.
Replying and resolving
Every app you connect can reply to comments and resolve them, as well as read them.
- It writes as you. A reply carries your name, with the app's beside it ("via Claude") in the thread, in comment emails and in CSV and PDF exports, so reviewers can tell it apart from one you typed. A resolved comment shows as resolved by you.
- It reaches only the comments you could reply to or resolve yourself, and it cannot edit or delete anything.
- Once it has fixed what a comment asked for, it resolves the comment with a reply starting "✅ Fixed:" and one sentence on what changed. It leaves open what it could not do, and asks the reviewer in a reply when it needs an answer.
- You can edit or delete its replies, and reopen what it resolved, as with your own.
What it can see and do
It sees exactly what you see in the dashboard: the layers you own or were invited to, the default Public layer of each site whose key is yours, their comments and replies with who wrote them, the picture taken of the page with each comment, and the images people attached. Nothing else on your account.
It can reply and resolve, as you, and never edit or delete anything. That is enforced by SharedLayers, not left to the app: the app never holds your SharedLayers session, only a token that works through this connector; every read runs in a read-only database transaction; and its replies and resolves go through the same rules as yours in the widget.
The app gets each comment's picture and attached images with the comment, and also as links it can download, save as files or give you to open, since you may not see what is attached. A link works for an hour, for that one image, without signing in, so treat it like a link you would share.
| Tool | What it answers |
|---|---|
list_layers | Your layers, grouped by site, with how many comments each has open. |
list_comments | The comments in one layer, on one site or across all of them, newest first. Open ones unless asked otherwise; filters for type, page and address (staging, UAT, production). Each gives the address it was left on, the page URL, the element it is pinned to as a CSS selector and a short label, and an id. |
get_comment | One comment in full, with every reply, a link that opens the page with the comment showing, the picture of the page and any images attached to the comment or its replies, each attached and as a download link that works for an hour. |
reply_to_comment | Adds a reply to a comment, as you, marked with the app's name. |
resolve_comment | Resolves a comment, as you, with a reply first when it has one. |
Disconnecting
Every app you have allowed is listed under Connect AI in the dashboard, with where it signs in from, when you allowed it, when it last read anything, and a Disconnect button. Disconnecting takes effect on the app's next request. Removing the connector in the app as well stops it from asking you to sign in again.
Each app is listed once. Connecting the same app again replaces its earlier connection. Removing the connector only in the app does not always reach SharedLayers (Claude does not say), so that connection stays listed until it has gone sixty days unused, or until you connect the app again or disconnect it here.
If something does not work
| What you see | What it means |
|---|---|
Claude Code does not list sharedlayers under /mcp | The session started before you added it. Start a new one in the same folder, or add it with --scope user to have it everywhere. |
| You cannot add a connector in Claude | Your organization lets only Owners add them. Send your Owner the note from Connect AI. |
| "SharedLayers does not know this app" | The app is using an old registration. Remove the connector from the app, add it again, and sign in once more. In Claude, also check that the OAuth client is set to Register automatically. |
| "This request has expired" | The sign-in waited more than ten minutes, or was already used. Start connecting again from the app. |
| "Create an account to connect apps" | You are signed in as a guest. Create an account, or sign in to the one your comments are in. |
| The app finds no comments on your app on localhost | Comments left on localhost are kept in the project's .sharedlayers folder, not by the connector (Apps on your computer). The connector says so, but an app working outside the project cannot open that folder. Start it in the project, or ask it to read .sharedlayers/layers. |
| The app asks you to sign in again | Its access renews itself while it is in use, and ends when you disconnect it or after sixty days without use. Sign in and allow it again. |