How to connect Claude to Winskel
Short answer
In Claude, open Customize, then Connectors, then Add custom connector. Name it Winskel, paste https://space.winskel.com/api/mcp, sign in, approve your Space access, then turn Winskel on in a new chat.
Steps
- In Claude, open Customize → Connectors → Add custom connector.
- Name it Winskel and paste the server address:
https://space.winskel.com/api/mcp. - Choose Sign in now and Register automatically, then approve your Space access.
- In a new chat, turn on Winskel under + → Connectors.
Check it works
Ask Claude: “Use Winskel to find my Space.” It should name the Spaces you can reach. To start one, ask: “Use Winskel to create a Space called My project.”
Good to know
- Sign in with OAuth and approve the Space or Spaces you want this connection to access.
- Connecting does not copy your private chat history into the Space.
- “Connected” means access is allowed. The app may still be closed.
Choose the right Claude setup
Use the connector in Claude for conversations in the Claude app. If you do your work in the Claude Code terminal, configure that client separately with the Claude Code setup guide. You can authorize both against the same Space if you use both. They still have separate setup and login states.
If the custom connector control is missing, check the Claude workspace you are in and whether its settings permit custom connectors. A workspace admin can confirm the policy. If Claude asks you to sign in again, reopen the Winskel connector in Claude and follow the offered sign-in action. Keep the canonical server URL unchanged.
If the approval page opens under the wrong Winskel account, cancel and switch accounts before continuing. After approval, start a new conversation with Winskel enabled. Try the read below before asking Claude to write a file or share a handoff.
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
- Is this the same as Claude Code?
- No. Claude Code connects with one terminal command. See the Claude Code guide.
- Do I need a paid Claude plan?
- You need a Claude plan that supports custom connectors. Your Claude subscription stays yours; Winskel never stores it.
Related guides
- Connect your AIHow to connect Claude Code to WinskelOne terminal command adds Winskel to Claude Code. Then authenticate with /mcp and share handoffs with your team's other AI apps.
- Connect your AIHow to connect ChatGPT to WinskelFind your installed Winskel plugin in ChatGPT, add it with OAuth for the first time, or reconnect it to the Space you want to use.
- How Winskel worksWinskel 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.