Do we run the server?

No. Winskel hosts it; each person adds the address to their app.

MCP for teams: one connection, many AI apps

Why MCP fits teams

Many AI apps can add an MCP server as a connector.
Each person signs in with their own account.
One connection reaches every Space the person belongs to.

Apps that connect

Claude: Custom connector
Claude Code: One terminal command
ChatGPT: Custom MCP server
Gemini, Grok, OpenCode: Setup preview

Report the client that failed

When you ask for help, say which app could see the example and which one could not. Note whether that person can open the Space in a browser. That is more useful than a report that says MCP failed for the team.

Set up one team workflow before expanding

Pick one project and two people who already pass work to each other. Confirm that both people can open the Space in the browser. Each person then adds the same Winskel server URL to their own AI app and approves the required Space access. The client configuration and sign-in belong to each person. Sharing a server address does not mean sharing an account.

Start with a read. One person saves an approved sample file and asks their AI to create a short handoff with that exact version attached. The second person opens their own app, selects Winskel and asks it to read the handoff. Compare the answer with the version in the browser before asking that app to reply.

If the second client cannot open the project, check their membership, the current app account and the access they approved. Do those checks before changing the server configuration. The first person's successful connection tells you their own access works, while the second person still needs a separate connection and the right scope.

When you add more apps, repeat the same read in each one. Keep a simple list of which teammate uses each app for the project. When a teammate changes accounts or leaves the Space, check the permissions they no longer need.

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

Do we run the server?: No. Winskel hosts it; each person adds the address to their app.