How to connect Claude Code to Winskel

Steps

1. In your terminal, run the command below.
2. In Claude Code, run /mcp, choose winskel and Authenticate.

Then try it

• “Use Winskel to find my Space.”
• “Create a Space called My project and share a handoff for the work I select.”
• “Check Winskel and continue in My project.”

What the connection can and cannot do

• It reads and writes your Spaces: handoffs, Markdown files and messages.
• It cannot see your Git repository or run tests. Merging happens in Git.
• User scope means the connection is available in every project on your computer.

Set up in the environment you actually use

Open the same terminal environment that you use for your project work. If your team uses separate local and remote environments, check where the Claude Code session actually runs before you add the server. A user-level configuration in one environment will not necessarily appear in another. Start Claude Code there and check the MCP list for the entry named winskel.

If the command fails before it adds a server, confirm the Claude Code executable and its version in that terminal, then review the command as pasted. If there is already an entry, check its address and authenticate the existing entry before you consider replacing it. Keep all unrelated MCP entries in place.

If winskel is listed but authentication is needed, open the authentication action in the MCP list. Confirm the Winskel account and approve the Space you want to use. Return to the same client and test a read. If the browser completed but the terminal still shows an old state, check the list again in a fresh Claude Code session.

When you work on a repository, keep repository access separate from the Winskel connection. Claude Code may already be able to read files in your working folder. To share something, have it save a small approved Markdown excerpt or summary in Space, then attach the exact version to a handoff. The next AI can use that shared note even if it works outside the repository.

Verify the connection before sharing work

Open the Space in your browser first. Confirm that you can see the project under the account you plan to authorize, and pick one harmless Markdown note for the check. In the AI app, open a new chat with Winskel available and ask it to find that named Space. Then ask it to read the note and tell you which version it used. Compare the answer with the Files panel.

Treat a successful sign-in and a successful read as separate checks. If the app says it connected but the Space is missing, confirm the app account, the Winskel account, and the scope you chose. Check them in that order before disconnecting or creating another entry. If a teammate owns the Space, check which account you accepted the invitation with and ask the owner to verify your membership.

For a failed setup, write down the app, the workspace, the step that failed and the exact error. Use the Space connection playbook to match the step. Leave passwords, access tokens, and private project text out of a support report.

Questions

Does Winskel get my code?

Only what your AI shares into the Space, such as Markdown files and handoffs. Winskel does not host or move your code.

Can Codex or Cursor connect too?

Yes. The steps are on the Connected agents page in Space.

Related guides

• Connect your AI→How to connect Claude to WinskelAdd Winskel to Claude as a custom connector in four steps, then share handoffs and files with your team's other AI apps.
• How Winskel works→Winskel and MCP: one connection for every AI appWinskel connects to AI apps over MCP, the Model Context Protocol. What the connection does, how sign-in works, and what it cannot see.
• How Winskel works→Agent reports and checks Winskel observedAI agents say things like “tests passed”. Winskel keeps what an agent reported apart from what it observed, and records human approvals.