Plugins & Connectivity
Connect to anything.
No exceptions.
L2H speaks every modern integration protocol — MCP and REST — in both directions. Every agent in your environment can reach any tool, any data source, and any system you can describe. If it has an endpoint, we can call it. If it doesn’t, we’ll wrap it.
∞
Integrations possible
MCP
Native, both directions
REST
Any HTTP-speaking system
SDK
Build your own plugins
Three paths. Zero limits.
Every system, every protocol, every direction.
You don’t pick from a catalog. You bring the systems you already run, and L2H meets them where they live.
MCP — both directions
Any MCP server. In or out.
Native Model Context Protocol support, both as a client and a server. L2H agents call any MCP-compatible tool — first-party, customer-built, or third-party. Expose your L2H workflows as MCP servers for Claude Desktop, IDEs, and any other agent framework to consume.
- Plug into the entire MCP ecosystem on day one
- Publish your workflows back out as MCP servers
- Future-proof — every new MCP tool works automatically
REST — anything that speaks HTTP
Any REST API. No glue code required.
If it has an HTTP endpoint, your agents can call it. OAuth 2.0, API keys, mTLS, signed webhooks, and SSRF guards are first-class. Connect to your CRM, ITSM, data warehouse, identity provider, billing system, or that one internal service nobody else can touch — without writing custom integrations.
- Every standard auth method, handled in config
- Typed credentials with scoped, expiring API keys
- Signed outbound webhooks for inbound triggers
Custom — built by you or by us
Build your own. Or we'll build it.
A declarative plugin manifest registers tool servers, workflow nodes, blueprints, and configuration — the same path L2H ships its own plugins on. Customer SDK for in-house teams. L2H Professional Services or partner-built for everything else.
- Customer plugin SDK with full developer docs
- L2H or partner-built bespoke plugins on request
- Same governance + approval flow as first-party plugins
What “unlimited” actually means.
Most platforms ship with a fixed connector list and a long roadmap of “coming soon.” L2H ships with a contract. Anything that speaks MCP or REST is already integrated — today, at signature. Ask us what we connect to, and the answer is the same: whatever you need.
- Identity providers (Okta, Azure AD, Ping, Keycloak)
- ITSM and ticketing (ServiceNow, Jira, Zendesk, Freshservice)
- CRM and revenue (Salesforce, HubSpot, Dynamics)
- Data and analytics (Snowflake, Databricks, BigQuery, Postgres)
- Cloud platforms (AWS, Azure, GCP, GovCloud)
- Collaboration (Slack, Teams, SharePoint, Confluence)
- Source control and CI (GitHub, GitLab, Bitbucket, Jenkins)
- Internal APIs your team built last quarter
Built for production from day one.
Connectivity without governance is a liability. Every plugin — first-party, customer-built, or partner-built — runs through the same security and approval plumbing.
Site-admin approval gate
No customer code reaches a worker without a designated site admin reviewing and approving the plugin manifest.
Workload-identity execution
Plugins run with workload-identity-bound credentials — no long-lived cloud keys, no shared service accounts.
Tool isolation per plugin
Each plugin runs in its own scope. A plugin only sees the tools, configs, and credentials it explicitly declares.
Append-only audit log
Every tool call, credential use, and configuration change is captured for ATO, SOC 2, and continuous compliance.
Customer plugin SDK.
Your team can build and ship plugins on the same path L2H does. A single declarative manifest registers everything a plugin contributes — tool servers, workflow nodes, blueprints, and configuration. Upload via the dashboard, site-admin reviews, synced into the platform on approval.
- Declarative manifest — tools, nodes, blueprints, config in one file
- Site-admin approval flow before any code reaches a worker
- Workload-identity-bound execution (no long-lived cloud keys)
- Tool isolation per plugin
- Same plumbing as first-party plugins — no second-class citizens
// Plugin manifest
One file. Tool servers, workflow nodes, blueprints, and any configuration the customer needs to provide — all declared in a single contract. The platform handles versioning, approval, and rollout.
Full developer documentation is available to customers and partners under their license. Need it built for you? L2H Professional Services and a network of trusted delivery partners are standing by.
What do you need to connect to?
Bring the systems your team already runs. We’ll show you, on a live call, exactly how L2H plugs into them — MCP, REST, or custom. No theoretical roadmaps. Working demos.