superglue for non-coders

superglue builds the connection between your systems. You tell it which connection you need in plain English, and it builds the integration and manages it for you.

The easiest way to get started with superglue is to talk to it. In case you still want an overview, here is a guide.

Good to know

System

The data source you connect to, for example BigQuery, Salesforce, Business Central, or SAP.

Tool

The connection itself. A tool performs one action against a system: read records, push data, run a report.

MCP server

Enables you to use tools you built in superglue in environments like Langdock or Claude Code, or share them with colleagues.

Credentials

Your personal access keys for a system. You always add your own, they are encrypted, and no AI sees them.

Find your way around

Six places you will use:

Agent. Where you spend most of your time. Ask it to build an integration or discover a system in plain language.
Tools. Your built connections and automations.
Systems. Which systems are connected to superglue. You can use a system, as soon as you have added your credentials.
Credentials. Your personal keys per system. You only see data you have credentials for. Here, you also can add your credentials.
Runs and Control Panel. Run history.
MCP Servers in the Control Panel. Build, manage, and export your MCP servers.

Create a tool

Open a new chat in the agent

The superglue landing page. To open a new chat, use the top right of the screen.
Describe what you want in plain language

For example: “I want to have my data from Salesforce in BigQuery.” Vague is fine; the agent asks back for whatever it needs.
Let the agent connect the source system

The agent asks permission and guides you through setup, so it can read the field names itself instead of guessing.
Choose how it runs

The agent offers options like real-time or on a schedule. Pick what suits the use case.
Iterate, then save the tool

The superglue agent inspects and tests each step, and confirms it with you. If you hit a wall in building a tool, ask in the chat how to proceed.

Add your credentials

A tool can only pull data once you give superglue access to the system. How that works depends on the system:

API key. A pop-up opens, you paste the key, and it is encrypted. AI never touches it.
OAuth or SSO. A login window opens (for example Salesforce). You log in there and superglue connects without ever holding a key.
Basic auth. You enter a username and password, both encrypted at rest.
Connection string. For databases like Postgres or MSSQL, you paste a connection string.

Credentials are personal. If a colleague shares a tool with you, you still need your own credentials to pull any data. You can only reach systems you already have access to; superglue cannot open a door that is locked for you.

Use a superglue tool in environments like Langdock

Build an MCP server

In the Control Panel, hit the plus, name the server, and add the tools you created. You can also ask the agent to create the MCP server for you in the chat.
Export it for Langdock

One click. Langdock and Claude Code use slightly different file formats, so pick the Langdock export. You get a file to import.
Import it in Langdock

Go to Integrations, then Add Integration, choose the file you exported, and import it.
Configure and add the connection

The tools from the MCP server appear automatically. Select the ones you need and add them.
Call the tools in chat

Ask your questions in plain language in Langdock and the tools run for you. No clicking around the source system.

Security and data

AI builds. AI is used only to build the connection. Once built, the connection runs as a fixed, deterministic process, like one built by a developer.
No data leaves your organization. Your data is only accessible to the people you give access to.
Self-hosted means self-contained. If you self-host superglue, it runs on your servers and nothing leaves your systems.
Permissions still apply. Existing permission sets carry over. You cannot reach data you do not have credentials for.