AI apps (MCP)
Connect VS Code to Clikso
In short
Press Add to VS Code below, or add Clikso to .vscode/mcp.json. VS Code asks you to sign in, and your browser opens Clikso to pick workspaces. Then use the Clikso tools from Copilot Chat in agent mode.
Connect VS Code to Clikso
Last checked 9 October 2026
https://app.clik.so/mcpYou need
- VS Code
- A recent version, with GitHub Copilot Chat.
- Clikso
- Any plan, including Free.
Add Clikso
Add the server
Press Add to VS Code above and confirm in VS Code.
Or run MCP: Add Server from the Command Palette. Choose HTTP, paste https://app.clik.so/mcp and name it clikso.
Or add it to your workspace by hand:
{
"servers": {
"clikso": { "type": "http", "url": "https://app.clik.so/mcp" }
}
}Sign in
VS Code asks to sign in to Clikso. Allow it, and your browser opens Clikso.
Tick the workspaces, choose View and make changes or View only, and press Allow access.
Try it
Open Copilot Chat and switch to agent mode. Ask something like "List my links in the Launch folder."
Approve changes in the chat
When a tool needs your approval, Clikso shows a card in the chat. It says "Clikso needs your approval" and shows exactly what will change. Press Approve and Clikso makes the change at once, or press Deny. See Approvals.
The card needs a VS Code sign-in that Clikso can verify, through vscode.dev. If the Clikso sign-in page called VS Code an "Unverified app", approvals come as a link to a Clikso page instead.
VS Code asks too
VS Code asks you to confirm before it runs a tool, unless you allow that tool. That prompt belongs to VS Code.
Clikso's settings apply on top of it, and Clikso's setting is the one enforced for every app. A tool set to Needs approval in Clikso still waits for your approval in Clikso.
Good to know
.vscode/mcp.jsonholds only the URL, so you can commit it. Each teammate signs in with their own Clikso account.- To stop, remove Clikso from
mcp.json. Then press Disconnect in Clikso under Settings → AI connections.