How do AI agents use CustomJS through Open Connector?

Your user connects CustomJS once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes CustomJS tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a CustomJS MCP server?

Yes. Open Connector can serve CustomJS as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call CustomJS actions with credentials injected server-side.

Where do CustomJS credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

CustomJS integration

CustomJS integration for AI agents.

CustomJS integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves CustomJS tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real CustomJS actions, managed and audited.

Your user connects CustomJS once; your agent can then the automation platform that lets you create and integrate custom JavaScript logic into Make.com, n8n, or as an HTTP API, and use it to integrate custom logic, generate PDFs, or capture screenshots in any software — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants CustomJS access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported CustomJS tools.

0 tools are generated from the published CustomJS catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.

No tools match “”.

FAQ

CustomJS integration, answered

How do AI agents use CustomJS through Open Connector?: Your user connects CustomJS once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes CustomJS tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a CustomJS MCP server?: Yes. Open Connector can serve CustomJS as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call CustomJS actions with credentials injected server-side.
Where do CustomJS credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents CustomJS — keep the keys.

Open source, self-hostable, with CustomJS credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →