Long-tail integrations — Live, HTTPS, MCP, import

Layer 1 — Live connectors

Layer 2 — Universal HTTPS / Custom Connector

Any REST API: paste base URL + key in Swarm HTTP / Custom Connector nodes. SSRF-safe fetch. Prefer this over waiting for a first-party OAuth app.

Layer 3 — MCP client (call external tools)

Layer 4 — Import / user-hosted runner (hybrid self-host)

Import n8n / Make / Zapier JSON into Swarm (structure maps; credentials stay FuseIQ work). Or call your self-hosted n8n/Activepieces via HTTP webhook from Swarm — FuseIQ stays the governance layer. We do not open-source the full multi-tenant SaaS to match Dify; hybrid is the ownership-smart path.

Before import, Swarm auto-saves a version snapshot so you can roll back (⌘H). Engineer runbook: hybrid runner (customer n8n docker → Swarm HTTPS → proof on FuseIQ).

FuseIQ as MCP server (external hosts)

External agents (Claude Desktop, Cursor, custom hosts) can call FuseIQ over HTTP JSON-RPC:

• Endpoint: POST https://fuseiq.io/api/mcp
• Auth: x-api-key: sk_fuseiq_… from Settings → API tokens
• Tools: fuseiq_list_runs, fuseiq_list_workflows, fuseiq_list_approvals, fuseiq_start_work

Do not claim

Catalog size ≠ Live OAuth count. We never market “3,000 native connectors” unless first-party or user-owned runners make them real.