superglue for non-coders

superglue connects your systems and turns plain-language requests into reusable tools. Start by telling the agent what you want to accomplish; it guides you through connecting systems, adding credentials, testing the result, and choosing how the tool should run. This guide explains the main concepts and screens you will use along the way.

Good to know

System

An API, database, file server, or other service that superglue can interact with.

Tool

A saved, repeatable action that reads or writes data through one or more systems.

Credential

A named set of secret values that grants access to one system.

MCP server

A collection of tools that AI clients can discover and run through MCP.

Find your way around

The main areas of the superglue app are:

1. Agent: Describe what you want to build, ask questions, or investigate a failed run in plain language.
2. Systems: View and configure the APIs, databases, file servers, and other services connected to superglue.
3. Credentials: Add or manage the named credentials that grant access to each system.
4. Tools: Review, test, and manage the reusable actions built across your systems.
5. Runs: Inspect execution history, results, timing, and errors.
6. Control Panel: Manage schedules, MCP servers, access rules, and organization settings.

Create a tool

1. Start a conversation with the agent

   Open a new chat and describe the outcome you want.

2. Explain the task in plain language

   For example: “Move new Salesforce accounts into BigQuery.” A rough description is enough; the agent asks for missing details.

3. Connect the required systems

   The agent helps configure each system and asks you to add credentials when access is required.

4. Review and test the tool

   The agent builds the steps, tests them with you, and shows what the tool will read or change before you save it.

5. Choose how the tool runs

   Run it on demand, schedule it, trigger it with a webhook, or expose it through an MCP server.

Add credentials

A system declares the secret names it needs, such as an API token, username, or password. A credential contains the corresponding secret values and belongs to that system. One system can have multiple named credentials, so different users or accounts can use the same system configuration without sharing secret values.

How you connect depends on the system:

• API token: Enter the value when prompted; superglue stores it encrypted.
• OAuth or SSO: Sign in with the provider and approve access; superglue stores the resulting tokens securely.
• Username and password: Enter both values as encrypted secrets.
• Connection details: Add the host, database, username, password, and other values required by the data source.

When a tool runs, superglue uses the credential selected for each system or your default credential. Secret values are not included in agent prompts.

Use a tool in Langdock

1. Create an MCP server

   In the Control Panel, create an MCP server and add the tools you want to make available. You can also ask the agent to do this.

2. Export it for Langdock

   Choose the Langdock export format and download the generated configuration.

3. Import it into Langdock

   In Langdock, open Integrations, add a new integration, and import the configuration.

4. Add the connection

   Select the imported tools you want to expose and finish the connection setup.

5. Use the tools in chat

   Ask for the data or action you need in plain language. Langdock calls the appropriate superglue tool.

Security and access

• Saved tools are deterministic: The agent helps build and test the configuration; saved runs execute that configuration consistently.
• Secret values stay protected: Credentials are encrypted, and their values are not placed in agent prompts.
• Access still applies: Users can run tools only with systems, credentials, and other resources they are allowed to use.
• Self-hosted deployments stay under your control: The application, data, credentials, and execution infrastructure run in your environment.

i

If you are unsure where to start, describe the outcome you want in the agent chat. It will guide you through the required systems, credentials, and tool steps.