Skip to main content

Latenode

Build, run and debug your Latenode scenarios, or call a scenario's own MCP tools, through Latenode's MCP server.

Connect it with: MCP. Latenode's own documentation: https://documentation.latenode.com/mcp-server/overview.

What agents can do​

Connect Latenode so the agents working your tasks can reach it. With it connected, they can:

  • Read a scenario's nodes by its ID, and create, change, activate or release a scenario from a task.
  • Run a scenario, one node, or a single app action without building a scenario.
  • Read a scenario's execution history and a run's status, error and node outputs to debug a failure.
  • Call the tools a scenario publishes through its own MCP Trigger.

Before you start​

  • A Latenode account, and a token made at app.latenode.com/mcp (Latenode asks for its expiry date).
  • For one scenario's tools: a saved scenario with an MCP Trigger, and its Server URL.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Latenode​

Jaah connects to Latenode with an access token, not with a sign-in button.

Connect with an API key​

Find each value first:

  • Server URL (optional): Leave blank for Latenode's own MCP server. To use one scenario's tools instead, paste the Server URL shown on that scenario's MCP Trigger.
  • Transport (optional): Only with your own Server URL: streamable_http, or sse if Test cannot complete the handshake. Leave it blank for streamable_http.
  • Token: For Latenode's MCP server: open app.latenode.com/mcp, select Create Token and copy it, as Latenode shows it once. For an MCP Trigger: the API key set under its Authentication.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Latenode card.
  2. Name the secret and choose who can use it.
  3. Fill in Server URL, Transport, Token.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Latenode with an access token, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah makes one read-only call to Latenode with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: url, transport, api_token.

Tell the agent in your task description which secret to use, for example “use the Latenode secret org/latenode”.

Latenode also runs an MCP server, which gives agents ready-made Latenode tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:

  1. Open the project and its MCP tab.
  2. Select Link, pick the Latenode secret, and confirm.
  3. New tasks on the project start with the Latenode tools. Tasks already running keep the tools they started with.

Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Latenode once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Latenode's side too, revoke the token at Latenode.

Limitations​

  • Latenode tokens have no scopes: a token can do anything its Latenode account can.
  • Runs started by agents use your Latenode plan's credits, and a single action is cancelled after 100 seconds.
  • Latenode's MCP server has no tool that lists scenarios: give the agent the ID of the scenario to work on.
  • A scenario's MCP Trigger must have Authentication turned on, so this secret holds its API key. A trigger with Authentication off lets anyone with its Server URL call its tools.
  • Agents can do only what the connected Latenode account allows.

Troubleshooting​

Test says Latenode rejected the token (401)

The token was revoked, reached its expiry date or was mistyped. Make a new one at app.latenode.com/mcp, or copy the MCP Trigger's API key again, and select Replace on the secret.

Test cannot complete the MCP handshake with a scenario's Server URL

Set Transport to sse under Advanced and test again. If it still fails, save the scenario and copy the Server URL from its MCP Trigger again.

New tasks on the project have no Latenode tools

Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.

Still stuck? Select Test and read the result: it names the value Latenode refused and the status it answered.

FAQ​

What does Test do?

It opens an MCP session with the server and lists its tools, then closes the session. It runs no scenario.

Can I connect both Latenode's server and a scenario's MCP Trigger?

Yes. Add one secret for each, then link each to the projects that need it.

Can a Latenode scenario start a Jaah task, or react when one finishes?

Yes, without this secret. A Webhook automation in Jaah takes calls from Latenode's HTTP Request node, and a Jaah webhook can call a Latenode Webhook trigger. The Automations guide Start tasks from Latenode walks through both.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Latenode account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.