Skip to main content
The core idea of superglue is to let users connect their systems via a natural language interface that abstracts away the pain of authentication, structuring requests and mapping data between systems. This page explains key concepts - systems and tools - that are the essential building blocks of everything superglue does.

​
Systems

Systems are the reusable building blocks for tools in superglue. A system represents anything that can provide, store, or process data: REST APIs, GraphQL endpoints, SOAP services, SFTP servers, Postgres databases, Redis instances, and more. Instead of maintaining a limited connector library, superglue takes a more general approach. Users can configure any system with custom documentation, URLs, authentication, and instructions tailored to their use case. Think of systems as containers that store all context required to interact with an external service. To learn more about creating systems, check the systems guide.

​
Tools

superglue is an AI-powered tool builder that builds on top of a user’s systems. Tools are built according to user instructions and execute sequentially. Every tool takes a number of (optional) inputs, executes a series of tool steps and returns an output. Tool inputs can include the systems that this tool will use, a payload of tool variables (e.g. a timestamp, a user ID or something similar) or files. Tools will execute deterministically once they are saved, but are built and auto-evaluated using large language models. For more details on tool building, please check out our tool guide.

​
Runtime

superglue is not just a tool builder, it’s the execution environment where your tools run. When you execute a tool, superglue handles the entire data pipeline: making API calls, resolving credentials, managing retries and rate limiting, and logging results. You don’t need to host your own workers, manage queues, or set up cron infrastructure. Tools can be triggered through multiple access points: the REST API, the TypeScript and Python SDKs, Model Context Protocol (MCP) for AI agents, the CLI, or directly from the UI. For automated execution, superglue supports cron-based schedules and incoming webhooks. Every execution, whether triggered manually or on a schedule, produces a run record with step-by-step logs, timing, and full request/response details. To learn more about running tools, see the deploying a tool guide.

​
Agents

Definitions of agents vary. When mentioning agents in superglue, we are referring to a chat-based interface to an LLM with access to a set of custom tools that it can execute on our user’s behalf. The superglue agent is designed to help you understand what superglue is, how to set up your systems in superglue and how to build tools tailored exactly to your needs and specifications. Different agents in superglue may have slightly different tool calling capabilities and context about your tools and systems, but the core concept remains the same.