For: everyone. Every role may hold their own MCP connection, members included — this is the one workspace connection a member can create.
MCP is the way your playbooks and personas become available inside Claude Desktop, Claude Code, Cursor, VS Code, Codex and any other client that supports it. There is one endpoint, and each person connects their own client to it.
Setting it up
Go to Settings → MCP Server. The endpoint URL and a ready-made config snippet are both there.
In your tool, add it as a custom MCP server.
Some clients then ask you to sign in; others want a key, which you create on the same Settings page. Which one your client does depends on the client, so follow whichever it asks for rather than preparing one in advance.
Nothing about this is configured inside sqemes beyond creating the connection — the rest happens in the other tool.
What the client can then do
It gets tools for searching and fetching your playbooks and personas — search_templates, get_template, list_personas, get_persona and others, depending on what your key is allowed to do.
This is the most capable of the three channels, because the client can find the right playbook mid-task without anybody choosing it from a list. It is also the only one besides sqemes Chat where personas work.
A connection belongs to one person
This is the part worth understanding properly. A connection is bound to the person who created it, and the server answers with that person's playbooks — not the workspace's.
So sharing a connection string with a colleague does not give them their own view; it gives them yours, under your name. Everyone creates their own. It takes a minute and it keeps access rules meaning what they say.
Two ways a working connection stops working
It went dormant. A connection unused for 90 days is refused rather than deleted. If something that worked months ago now returns nothing, create a new connection.
The person left the workspace. Connections go with their owner. That is the intended behaviour — it is also why a shared connection string is a bad idea, because it stops working for reasons the person using it cannot see.
If the client connects but finds nothing
Check in this order: the key's permissions, whether you personally have access to the playbooks you are expecting, and whether the connection is pointed at the workspace you think it is. A connection that authenticates cleanly and returns an empty list is almost always an access question, not a setup one.
Updated 27 September 2026 · Article version 1