
Lichess.org Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_SihStiXr6SWwvQjRnQi6dJGY8eJOVBZFzF5K4U8S/mcpConnecting Lichess.org to Windsurf
About a minute, in Cascade
- 1In Cascade, click the MCPs icon (or go to Settings, Cascade, MCP Servers).
- 2Edit mcp_config.json and add Lichess.org with the serverUrl field set to your link. The link above is the URL.
- 3Save and ask something real. Lichess.org is now part of Windsurf.
{
"mcpServers": {
"lichessorg-open-chess-intelligence-mcp": {
"url": "https://edge.vinkius.com/vk_preview_SihStiXr6SWwvQjRnQi6dJGY8eJOVBZFzF5K4U8S/mcp"
}
}
}Windsurf + Lichess.org
One chat. Your Lichess.org, live inside Windsurf.
Real prompts, answered with live data. This is the kind of session you will have in Windsurf once the server is in.
Waiting for input…
Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.
These prompts ship with the Lichess.org Connector. Once yours is connected, they work in your sessions.
The full capability set, the prompts and the observed latency live on the Lichess.org Connector page.
Mission Control
See everything your Windsurf agents do in Lichess.org.
When Windsurf runs a tool in Lichess.org, it happens in your editor: you see the result, but not the request itself, what data it carried, or whether a rule was broken.
Now every move lands on your screen.
Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.
Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.
AI Agents Activities
last 30 daysRequest Volume & Latency
requests latencyEvery request your Windsurf agents make through Lichess.org is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Lichess.org workflows.
What sets us apart
It's not just the Connector that stays safe. Everything your agents do through it is.
Connecting Lichess.org to your AI is step one. But an open line between your agents and Lichess.org is only half the story: without protection, every action they take runs unguarded.
That's why protection doesn't stop at the door.
Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.
Tamper Proof Activity Log
Every request your agents make in Lichess.org is recorded and signed, so any change to the history becomes detectable.
Automatic Key Rotation
We rotate security keys every 24 hours. Your Lichess.org connection stays protected without any manual work.
Spending Protection
We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your Lichess.org actions never surprise you.
Isolated Sandbox
Every execution through Lichess.org runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.
Security Event Streaming
Security events flow to Splunk, Datadog or your own webhook, so Lichess.org activity lands in the tools you already rely on.
Instant Resume
Idle connections resume in 3 to 5 ms while preserving their state, keeping your Windsurf sessions responsive.
Malicious File Protection
We detect compressed files designed to exhaust system resources and block them before they ever reach Lichess.org.
Credential Validation
We test your Lichess.org credentials before saving them. Invalid credentials are rejected instead of being stored.
Separate Usage Limits
Usage stays isolated per account, so activity in one connection never consumes another account's allowance.
One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.
These guarantees are not add-ons: they are the infrastructure every Lichess.org connection runs on. Read how our infrastructure protects everything your Windsurf agents do, end to end.
Inside Vinkius
Get Lichess.org ready for your AI. It's easy.
You choose Lichess.org from the Vinkius Catalog, sign in to your Lichess.org account, and get one connection link. That's it.
You choose Lichess.org
You find Lichess.org in the Catalog and install the Connector with one click.
Lichess.org
Active
Enable ConnectorActivating…You sign in
You connect your Lichess.org account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
RequiredEncryptedSave & ContinueYou add the link in Windsurf
Vinkius gives you one connection link. In Windsurf, you add Lichess.org to mcp_config.json with the link in the serverUrl field, and the connection is ready.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_SihStiXr6SWwvQjRnQi6dJGY8eJOVBZFzF5K4U8S/mcpGo to DashboardConnection Token
vk_live_••••••••
Set it up once. Use Lichess.org with the AI you already use.
FAQ
Windsurf access questions.
- 01
Where does this work?
In Cascade: the MCPs icon or Settings, Cascade, MCP Servers, with the config in ~/.codeium/windsurf/mcp_config.json and the serverUrl field for remote servers.
- 02
If I connect Lichess.org to Gemini, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Lichess.org is already there.
- 03
Do I need to hand my Lichess.org password to Gemini?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Gemini only ever sees the link, and you can remove it whenever you want.
- 04
What can I actually ask Gemini to do with Lichess.org?
Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.
- 05
Gemini doesn't show the Connector. What do I check?
Make sure the entry was saved in mcp_config.json with the serverUrl pasted exactly as copied, then confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.
- 06
Can I remove the access later?
Remove the entry from mcp_config.json and it's out of Cascade. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about Lichess.org? The Connector page answers them. See everything the Lichess.org Connector can do
About the Connector
What Lichess.org adds to your AI.
Once you connect it, your AI gains 10 capabilities: the exact actions it can take in Lichess.org when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.
See everything the Lichess.org Connector can do