Personas work in Claude Code, Cursor and Codex, too. See how
  1. Home
  2. Comparisons
  3. sqemes and Claude

sqemes and Claude: better together.

Claude is where many teams write, analyse and code. sqemes keeps your team's skills, prompts and personas once and brings them into Claude, Claude Code and every other AI tool you use.

In short: keep Claude, add your know-how.

Claude can connect remote MCP servers as custom connectors on every plan. That is how sqemes works inside Claude. The browser extension works on the Claude web app as well.

  • Claude is where your team can chat, work in projects and use skills
  • sqemes is where your team keeps its know-how as skills, prompts and personas, with versions and rights
  • As a custom connector, sqemes lets Claude search and load your playbooks during a task
  • In Claude Code, the same MCP server brings your conventions to every developer
  • The same playbooks also work in ChatGPT, Gemini, Cursor and sqemes Chat

How they work together.

Three steps on Claude Team or Enterprise.

Step 1

Keep it in sqemes

Write skills, prompts and personas once. Every saved change keeps a version, and you decide who may see and who may edit each one.

Step 2

Add sqemes as a connector

On Team, an owner adds sqemes as a custom connector. Then each member connects their own account. On Pro and Max, everyone adds it themselves.

Step 3

Use it everywhere

In Claude, Claude Code and every other tool connected to sqemes, the AI loads the playbook the task needs. A change in sqemes reaches all of them.

Side by side.

FeaturesqemesClaude
What it isA library for AI know-how: skills, prompts and personas, used in other AI tools and in sqemes ChatAn AI assistant with chat, projects, skills and Claude Code
Where the know-how is usedIn Claude, ChatGPT and Gemini through the browser extension, any MCP client, sqemes ChatIn the Claude apps and Claude Code, and in Claude's Microsoft 365 add-ins
Reusable knowledgeSkills with files, loaded when a task needs themSkills that load when a task calls for them; projects with their own knowledge
SharingPer playbook: everyone, named people and groups, or only me; who may edit is set separatelyOwners provide skills for everyone; projects are shared with view or edit rights on Team and Enterprise
MCPAn MCP server for your playbooks and personas; sqemes Chat also connects other MCP serversConnects remote MCP servers as custom connectors on every plan; on Team, owners add them
ModelsAny provider with your own key, or the plan's AI creditsAnthropic's Claude models
TrainingYour content is never used to train a modelInputs and outputs of the commercial products are not used for training by default
HostingHosted in the EU; self-host on your own servers under a fair-code licenseData stored in the US, according to Anthropic

As of: 15 November 2026, from Anthropic's own pages. Sources: Anthropic: custom connectors, Anthropic: skills, Anthropic: projects, Anthropic: server locations, Anthropic: model training.

When which fits.

Most teams use both. This helps if you wonder whether Claude alone is enough.

Claude alone fits when

your whole team works in Claude and nowhere else.

  • Everyone uses the Claude apps and Claude Code
  • Owners manage skills for the organisation in Claude
  • You do not need the same know-how in other tools

sqemes fits when

your know-how should work in Claude and beyond.

  • Teams use different tools: ChatGPT, Claude, Gemini, Copilot, Cursor or a platform like logicc
  • Personas should load the right playbook by themselves
  • Every change needs a version you can restore
  • You want to run it on your own servers

More comparisons.

Questions, answered.

What teams ask about sqemes and Claude.

Still unsure?

Write to us. A real person answers.

Contact us
01How do we get sqemes into Claude?
As a custom connector. On Team, an owner adds sqemes once, then each member connects their own account. The browser extension also works on the Claude web app.
02Does it work in Claude Code?
Yes. Claude Code connects to the sqemes MCP server like any other MCP client and loads your playbooks while it works.
03Claude has skills too. Why sqemes?
Both have skills. sqemes keeps them once and brings them into Claude and every other tool connected to it, with versions and rights per playbook.
04Where is our data stored?
sqemes stores your workspace in the EU. For Claude, Anthropic states that data is stored in the US.
05Who wrote this comparison?
sqemes. Every statement about Claude comes from Anthropic's own pages, linked below the table, as of November 2026. If something has changed, tell us and we correct it.