Skip to main content
superglue exposes saved tools through Model Context Protocol (MCP). MCP clients can discover available tools, inspect their input schemas, and execute them directly.
MCP exposes saved tool discovery and execution. It does not create systems, edit tools, or manage access rules.

​
Endpoint

Use the MCP endpoint shown in the Deploy modal for your environment.
EnvironmentEndpoint
superglue Cloudhttps://api.superglue.cloud/mcp
Self-hostedhttps://your-api.example.com/mcp
The MCP endpoint is the API endpoint with /mcp appended. Enterprise deployments can also expose named MCP servers from Control Panel → MCP Servers. Named servers have their own endpoint: 
https://your-api.example.com/mcp/{orgId}/{serverName}
Use named servers when you want to export a specific set of saved tools instead of the default all-tools endpoint. Named servers can also be managed from the CLI: 
sg mcp list
sg mcp create --name sales-tools --tool get_customer --tool create_invoice
sg mcp edit --id <serverId> --add-tool another_tool
For self-hosted instances, configure the CLI with that instance’s API endpoint: 
export SUPERGLUE_API_ENDPOINT="https://your-api.example.com"
export SUPERGLUE_API_KEY="your-api-key"

​
Client Config

For clients that support remote HTTP MCP servers: 
{
  "mcpServers": {
    "superglue": {
      "type": "http",
      "url": "https://api.superglue.cloud/mcp"
    }
  }
}
Claude Code can add the same server directly: 
claude mcp add --transport http superglue https://api.superglue.cloud/mcp
Use your own deployment endpoint instead of the Cloud endpoint when running self-hosted superglue.

​
Authentication

The default /mcp endpoint accepts the same superglue API keys used by the REST API. API keys can be restricted by access rules and revoked from the superglue app. Enterprise deployments also support MCP OAuth for clients that implement the MCP authorization flow. In that setup, the MCP server advertises protected-resource metadata, dynamic client registration, token, JWKS, and userinfo endpoints; authorization opens the web app for sign-in and consent. Named MCP servers support two authentication modes:
  • OAuth Login: each MCP user logs into their own superglue account through the MCP OAuth flow.
  • API key: the MCP client sends Authorization: Bearer <SUPERGLUE_API_KEY> and authenticates as the MCP server creator. The key must be active and assigned to that creator.
API-key named servers disable MCP OAuth discovery and do not expose the authenticate helper tool.

​
Available Tools

MCP exposes saved tools that the authenticated user or API key can access. Tool names are derived from saved tool ids, and each tool uses its configured input schema. Named MCP servers store a selected list of tool ids, but RBAC is still enforced at connection and execution time. The callable tool set is the intersection of the named server’s selected tools and the authenticated user’s or API key owner’s allowed tools and systems. MCP-triggered executions create normal superglue runs, so they appear in run history and follow the same access rules as executions started from the app or API.

​
Next Steps

  • Create or edit tools in the superglue app.
  • Copy your deployment-specific MCP endpoint from the Deploy modal, or create a named server in Control Panel → MCP Servers.
  • Use Export on a named server to download setup configs for Langdock, Claude Code, Cursor, and Codex.
  • Add the server to your MCP client using API key auth or Enterprise OAuth.