superglue exposes your tools through Model Context Protocol (MCP) , giving AI agents direct access to execute pre-built superglue tools.
The MCP interface provides discovery and execution of pre-built superglue
tools. It does not support ad-hoc integration 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 Workflows Give AI agents the ability to discover and execute complex multi-system
workflows without manual API wiring.
Internal Tooling Expose business logic as AI-accessible tools for customer support, ops
teams, or automated workflows.
Installation Cursor Add to your Cursor MCP settings (.cursor/config.json or via Settings → MCP):
{ "mcpServers" : { "superglue" : { "command" : "npx" , "args" : [ "mcp-remote" , "https://mcp.superglue.ai" , "--header" , "Authorization:${AUTH_HEADER}" ], "env" : { "AUTH_HEADER" : "Bearer YOUR_TOKEN_HERE" } } } }
Claude Desktop Add to Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{ "mcpServers" : { "superglue" : { "command" : "npx" , "args" : [ "mcp-remote" , "https://mcp.superglue.ai" , "--header" , "Authorization:${AUTH_HEADER}" ], "env" : { "AUTH_HEADER" : "Bearer YOUR_TOKEN_HERE" } } } }
Self-Hosted Point to your self-hosted instance:
{ "mcpServers" : { "superglue" : { "command" : "npx" , "args" : [ "mcp-remote" , "http://localhost:3000/mcp" , "--header" , "Authorization:${AUTH_HEADER}" ], "env" : { "AUTH_HEADER" : "Bearer YOUR_TOKEN_HERE" } } } }
Get your API key from the superglue web application sidebar under API
Keys .
The MCP server exposes two core tools for discovery and execution:
Search for pre-built tools using natural language queries.
Input Schema: { searchTerms : string ; // Space separated search terms }
Returns: { success : boolean ; tools : Array <{ id : string ; name : string ; description : string ; integrations : Array <{ id : string ; name : string ; type : string ; }>; }>; }
Use Cases:
Discover available tools for a specific task
Browse all tools (use * as wildcard)
Find tools by integration type or capability
Example: { "searchTerms" : "sync shopify orders to postgres" }
Execute a saved tool by its ID.
Input Schema: { id : string // Tool ID to execute payload ?: Record < string , any > // Optional JSON payload }
Returns: { success : boolean data ?: any // Execution result (truncated if > 20KB) error ?: string // Error message if failed suggestion ?: string }
Behavior:
Executes with saved credentials from integrations used during build
Self-healing disabled by default for deterministic results
Full execution logs available in superglue dashboard
Example: { "id" : "tool_abc123" , "payload" : { "startDate" : "2024-01-01" , "endDate" : "2024-01-31" } }
Usage Patterns Discovery → Execution Flow // 1. Find relevant tools superglue_find_relevant_tools ({ searchTerms: "customer data from salesforce" , }); // 2. Execute the tool superglue_execute_tool ({ id: "tool_xyz789" , payload: { accountId: "001..." }, });
Troubleshooting Connection Issues # Test MCP endpoint curl https://app.superglue.cloud/mcp \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
Error: "Tool ID does not exist"
Solution: Use superglue_find_relevant_tools to get valid tool IDs or check the dashboard.Next Steps 
