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

sqemes and Langdock: better together.

Langdock is an AI platform from Berlin with its own chat, agents and workflows. sqemes keeps your team's skills, prompts and personas once and brings them into every AI tool you use, Langdock included.

In short: one library for every tool.

Langdock can connect remote MCP servers. That is how sqemes works inside Langdock, the same way it works in ChatGPT, Claude or Cursor.

  • Langdock is where your team can chat, run agents and build workflows
  • sqemes is where your team keeps its know-how as skills, prompts and personas, with versions and rights
  • Connected over MCP, the AI in Langdock can search and load your sqemes playbooks during a task
  • The same playbooks also work in ChatGPT, Claude, Gemini, Cursor and sqemes Chat
  • Useful when not everyone in the company works in the same AI tool

How they work together.

Three steps, if you use both.

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

Connect sqemes in Langdock

Add sqemes as a remote MCP server under integrations in Langdock. There, adding one needs the right to create integrations, which editors and admins have.

Step 3

Use it everywhere

In Langdock and in 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.

FeaturesqemesLangdock
What it isA library for AI know-how: skills, prompts and personas, used in other AI tools and in sqemes ChatAn AI platform with its own chat, agents, workflows and integrations
Where your team worksIn the tools it already uses: ChatGPT, Claude and Gemini through the browser extension, any MCP client, sqemes ChatIn Langdock: web, desktop and mobile apps, Microsoft add-ins, Slack and Teams bots
Prompts with fields to fill inYesYes, in the prompt library
Reusable knowledgeSkills with files, loaded when a task needs themSkills, activated by their description; admins can make some mandatory
RolesPersonas: a working role that loads the right playbook when its condition appliesAgents: specialised assistants with instructions, knowledge and integrations
Versions and rightsEvery saved change keeps a version you can restore; who may see and who may edit, per playbookPrompt folders private, for the workspace or for a group; admins share skills with the whole workspace
MCPAn MCP server for your playbooks and personas; sqemes Chat also connects other MCP serversConnects remote MCP servers; its own MCP server offers its agents
ModelsAny provider with your own key, or the plan's AI creditsMore than 40 models from several providers, own keys possible
HostingHosted in the EU; self-host on your own servers under a fair-code licenseHosted in the EU on Microsoft Azure; dedicated and on-premise deployments for large customers

As of: 14 November 2026, from Langdock's own pages. Sources: Langdock MCP docs, Langdock agent MCP server, Langdock prompt library, Langdock skills, Langdock models, Langdock security.

When which fits.

Many teams can use both. If you choose one, this helps.

Langdock fits when

your company wants one AI platform where everyone works.

  • Everyone should work in the same chat, with agents and workflows
  • You want a provider with ISO 27001 and SOC 2 Type II
  • You need a dedicated or on-premise deployment for a very large number of seats

sqemes fits when

your know-how should work in every AI tool, not only in one.

  • Teams use different tools: ChatGPT, Claude, Gemini, Cursor or Langdock
  • 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

How sqemes reaches your tools.

Questions, answered.

What teams ask about sqemes and Langdock.

Still unsure?

Write to us. A real person answers.

Contact us
01Can I use sqemes inside Langdock?
Yes. Langdock can connect remote MCP servers. Add sqemes there, and the AI in Langdock can search and load your playbooks. In Langdock, adding an integration needs the right to create integrations.
02Do I need both?
No. Langdock works without sqemes, and sqemes works without Langdock. Together, your playbooks live in one place and reach Langdock and every other tool you connect.
03Both have prompts and skills. What is the difference?
Where they are used. sqemes keeps your playbooks once and brings them into every tool connected to it, Langdock included, with versions and rights per playbook.
04Where is our data stored?
sqemes stores your workspace in the EU. A chat request goes to the provider of the model you choose. Langdock describes its own hosting on its security page.
05Who wrote this comparison?
sqemes. Every statement about Langdock comes from Langdock's own pages, linked below the table, as of November 2026. If something has changed, tell us and we correct it.