Development entry points for connecting your function capabilities to different delivery channels. Use SDKs to plug local code into Connect, Cloud, MCP, and Fusion services instead of rewriting glue code.
Hand the same function capability over to OOMOL Cloud and reduce the infrastructure work behind service delivery.
Provide functions deployed on OOMOL Cloud directly as MCP tools for agent use.
Wrap blocks or function capabilities as MCP tool interfaces with less boilerplate between implementation and tool delivery.
Write function tasks in Python that run directly on OOMOL Cloud.
Call OOMOL Fusion APIs through one SDK and avoid rebuilding polling and async handling yourself.
Call OOMOL Fusion APIs from TypeScript and plug more capabilities into your functions or services.
Expose functions or services that already run locally, so remote API access and MCP access become direct and controlled.
Expose local functions as remotely callable MCP tools so agents use the capability exactly where it already runs.
Expose local functions or services as remote APIs, useful when you want to start locally and open access step by step.
