superglue exposes your tools through Model Context Protocol (MCP), giving AI agents direct access to execute pre-built superglue tools.Documentation Index
Fetch the complete documentation index at: https://docs.superglue.cloud/llms.txt
Use this file to discover all available pages before exploring further.
The MCP interface provides discovery and execution of pre-built superglue tools. It does
not support ad-hoc system creation or tool building. Use MCP in production for agentic use
cases and internal GPTs.
When to use MCP
Controlled Access
Execute only pre-approved, tested tools. No ad-hoc code generation or system modification.
Tool Execution in Production
Execute saved tools from your custom GPTs with full observability and error handling.
Agent Automation
Give AI agents the ability to discover and execute complex multi-system superglue tools without
manual API wiring.
Internal Tooling
Expose business logic as AI-accessible tools for customer support, ops teams, or automated
tasks.
Installation
Cursor
Add to your Cursor MCP settings (.cursor/config.json or via Settings → MCP):
Claude Desktop
Add to Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Self-Hosted
Point to your self-hosted REST API and add a /mcp path:Enterprise: MCP access inherits your org RBAC from the API key used for authentication. The
MCP server only exposes and executes tools that key is permitted to use.
Available Tools
The MCP server exposes:- Native MCP tools for each saved superglue tool (registered automatically at startup)
- An
authenticatehelper tool for end-user reauthentication flows
superglue tools (auto-registered as MCP tools)
Every pre-built superglue tool available to the authenticated API key is registered as its own MCP tool. How names are generated:- Tool names are derived from superglue tool IDs
- Non-alphanumeric characters are replaced with underscores
- Name collisions are resolved with numeric suffixes
- Uses each superglue tool’s payload schema when available
- Falls back to a permissive object schema for dynamic payloads
- JSON string content with
{ success, data }on success - JSON string content with
{ success: false, error }on failure - Large execution results are truncated before returning
- Executes with saved credentials from systems used during build
- Sends execution telemetry and logs to superglue
authenticate
Generates an authentication link to help users reconnect credentials when
execution fails due to missing auth.
Input Schema:
Troubleshooting
Connection Issues
Tool Not Found
tools/list.
Next Steps
Create a Tool
Build tools to expose via MCP
Creating a System
Connect and configure external systems
API Reference
Direct REST API access
Set Up Guide
Deploy self-hosted MCP server