MCP Builder

Build with your AI agent. Run automatically in the cloud.

Connect Claude Code, Cursor, or Codex through MCP. Describe the work once; events in your apps start the saved workflow in Latenode, even after you close your agent.

Your agent builds it. You connect your apps, test, and activate. Latenode handles the cloud execution, with every step visible and editable.

Start Free See connection steps

Cloud execution

Your apps trigger it. Latenode runs it.

A new contact in HubSpot. An email in Gmail. A file in Drive. Start with the event your team already works from.

Choose a built-in app trigger instead of running your own server or maintaining a webhook handler. Once connected, tested, and activated, your workflow runs in Latenode’s cloud.

Illustrative example

Build with your agent

Build a follow-up workflow for every new HubSpot contact.

Claude Code · Cursor · Codex

Connect, test, activate

Connect HubSpot and Gmail, check the fields, and test before switching the workflow on.

Run in Latenode’s cloud

HubSpot · New Contact

.mb-graph-visual { display: none; }HubSpot · New Contact → Latenode · Research company → Latenode · Qualify lead → HubSpot · Update Contact → Gmail · Create Draft

Triggers use instant events or polling, depending on the app and event.

No authoring session to keep open. No server to deploy or maintain.

What will you build?

Start with an app event. Finish with useful work.

The next lead, email, row, or document can start a process your team no longer has to repeat by hand.

Choose an example, then ask your agent to adapt the connections, rules, and outputs to your team.

.mb-case-tabs { display: none; } @layer base { .mb-explorer > .mb-case-panel[hidden] { display: grid !important; } } .mb-explorer > .mb-case-panel + .mb-case-panel { border-top: 1px solid var(--ln-border); }

Give every new lead a researched first response.

Sales gets company context, a qualification reason, and a draft it can review.

Your brief

When a contact is created in HubSpot, research the company, qualify the lead, update the contact, and save an introductory email in Gmail.

App trigger

HubSpot · New Contact

A new CRM contact provides the email and company domain.

Cloud workflow

.mb-graph-visual { display: none; }HubSpot · New Contact → Latenode · Research company → Latenode · Qualify lead → HubSpot · Update Contact → Gmail · Create Draft

Result

Updated CRM contact + Gmail draft

Company research, fit assessment, and a personalized first email, ready for human review.

Start Free

Start with a task from your own team.

Lower repeat costs

Use AI to build. Spend tokens only where AI is needed.

Rules, formatting, and app actions can run as ordinary workflow logic. Latenode meters that execution in CPU seconds.

Your coding agent builds the route once. Each new app event runs the saved steps without asking a model to reason through the same routine again.

Illustrative example

Build with Claude Code, Cursor, or Codex

When a HubSpot contact is created, check the routing rule, format the contact details, and notify the right Slack channel.

Saved workflowRuns on incoming events

Workflow execution: CPU seconds

No model steps in this route

Add AI where it helps

The lead research, qualification, and email writing shown above use AI. Those model steps have additional usage; the surrounding app actions and rules do not need a model.

Additional model usage

AI steps and paid-provider services incur additional usage charges.

Workflows and AI agents

Set the steps. Or let an agent choose its tools.

Use a workflow for a known sequence. Use a cloud AI agent when each new contact may need a different lookup.

Claude Code, Cursor, or Codex can build either approach. Both start from an app event and run in Latenode after you activate them.

Illustrative example

Workflow

A lead follows the steps you set.

.mb-graph-visual { display: none; }HubSpot · New Contact → Latenode · Research company → Latenode · Qualify lead → HubSpot · Update Contact → Gmail · Create Draft

Research, qualify, update, draft: AI works at defined steps, and the workflow controls their order.

AI Agent

An agent chooses the research it needs.

.mb-graph-visual { display: none; }Both patterns begin with HubSpot New Contact. The fixed workflow follows research, qualification, CRM update, and Gmail draft steps. The cloud AI agent can call company research and CRM context tools as needed, then save a lead brief.

Tools you configure

The cloud agent chooses from your configured tools to investigate the new contact, then saves its assessment to the CRM.

Apps, AI, and custom logic

Turn a new contact into a sales-ready brief.

Use the event’s contact ID, email, and company domain to connect research with the right CRM record and email draft.

Your builder agent can discover actions and their fields, then map outputs into the next step. You can inspect those mappings in the visual editor.

1,600+ app triggers

Choose the app and event that already signal work for your team.

Illustrative example

HubSpot · New Contact

contact_id: 1042
email: [email protected]
domain: northstar.example

Research + qualification

Company context: B2B software · 50–200 employees
Fit assessment: High fit for customer reporting automation
Reason: Matches the industry and team-size criteria you configured

Use your qualification criteriaHigh fit → Priority sales queue

HubSpot update + Gmail draft

Contact 1042: Company context and qualification reason saved
Gmail draft: Personalized introduction ready for review

JavaScriptHTTPNeed a custom format or API call? Add JavaScript or HTTP.

Visual control

See the workflow. Change it by hand or by prompt.

Open a node to inspect its condition, destination, or field mapping. Change it yourself, or ask Claude Code to update it.

Your team can follow the routing without reading generated code. Test changes in development while the published workflow keeps running.

Illustrative example

Claude Code

Route new HubSpot contacts with a high fit assessment to our priority sales queue. Keep the remaining contacts in the standard queue.

MCP actions

◇get_scenario◇update_scenario

New contact qualification

Current rule

HubSpot New Contact → Qualify lead → Standard queue

Requested change

.mb-graph-visual { display: none; }Illustrative Claude Code change: HubSpot New Contact starts the workflow. The lead fit condition routes high-fit contacts to the priority sales queue and other contacts to the standard queue. Inspect the field, match, and destination in the rule settings, and test before publishing.

Rule configuration

Field: Lead fit
Match: High fit
Destination: Priority queue

Development: test the changeProduction: published workflow

Cloud run history

Follow an app event through every step.

See what started a run, what each node received, and what it produced. The event, logs, and results stay together in Latenode’s cloud.

Open a run to inspect the data yourself, or ask your agent to help investigate it. Here, one new HubSpot contact becomes a qualified CRM record and a Gmail draft.

Illustrative example

Claude Code

Show me the cloud run for the new HubSpot contact and the draft it created.

Trigger event

HubSpot · New Contact · contact 1042

Company research and qualification are available in the run’s step data.

Success

Contact 1042 updated. Gmail draft saved for review. No email sent.

Gmail · Draft preview

To: [email protected]

A simpler way to automate customer reports

Hi Alex, I noticed Northstar builds software for growing teams. Would it be useful to explore automating customer reports across your apps?

Latenode

Execution history

Newest first

10:42 · Contact 1042SuccessSelected run
10:35 · Contact 1041Success
10:21 · Contact 1040Success

Read-only execution · HubSpot New Contact

.mb-graph-visual { display: none; }HubSpot · New Contact → Latenode · Research company → Latenode · Qualify lead → HubSpot · Update Contact → Gmail · Create Draft

Contact 1042 · Step data

Incoming event: HubSpot New Contact · contact_id: 1042 · [email protected]
Qualification: High fit · B2B software company, 50–200 employees; matches the configured criteria.
Result: HubSpot contact updated · Gmail draft saved · No email sent

Connect your agent

Connect your agent and start building.

Choose your client below and connect it to Latenode with MCP. Add the recommended builder skill, then describe your first workflow.

Start Free

.mb-guide-tabs, .mb-guide-copy-button { display: none; } @layer base { .mb-guide-panel[hidden] { display: block !important; } } .mb-guide-panel .mb-guide-client-heading { display: block; }

Create a Latenode token
Open the MCP page in your Latenode account. Create a token, choose its name and expiry, and copy it when it appears.
Open Latenode MCP
Connect your client
Replace YOUR_TOKEN_HERE in the command or configuration with your Latenode token before using it.
Claude Code
Run this command in your terminal. It makes the Latenode server available across your projects.
Terminal command
claude mcp add --transport http --scope user latenode https://platform-mcp.latenode.com/api/v1/mcp --header "Authorization: Bearer YOUR_TOKEN_HERE"
In Claude Code, run /mcp to check the server status.
Cursor
Create or open ~/.cursor/mcp.json. Add the latenode entry under mcpServers and keep any existing server entries.
~/.cursor/mcp.json
{ "mcpServers": { "latenode": { "url": "https://platform-mcp.latenode.com/api/v1/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN_HERE" } } } }
Save the file, then return to Cursor.
Other agents
Add an HTTP MCP server in your client’s settings using this URL and header. Follow your client’s configuration format.
Server URL
https://platform-mcp.latenode.com/api/v1/mcp
Authorization header
Authorization: Bearer YOUR_TOKEN_HERE
Find instructions for your client
Add the recommended builder skill
Run this from your project folder and follow the installer prompts. The skill adds Latenode’s scenario-building instructions for supported coding agents, including Claude Code and Cursor.
Terminal command
```
npx skills add latenode-com/skills --skill latenode-scenario-builder
```

Ask for your first workflow

Paste this into your connected agent, or replace it with a task from your team.

Build a Latenode workflow triggered by a new contact in HubSpot. Research the company, qualify the lead against my criteria, update the contact, and save a personalized introductory email as a Gmail draft. Ask me for the app connections, qualification criteria, and CRM fields to update. Keep the workflow inactive so I can inspect and test it first. Create drafts only; do not send emails.

Connect HubSpot and Gmail in Latenode. Check the trigger, qualification criteria, and field mappings, then test the workflow. Activate it when you’re ready: new HubSpot contacts will start cloud runs, even after you close your agent.

Build with your AI agent. Run automatically in the cloud.

Your apps trigger it. Latenode runs it.

Build with your agent

Connect, test, activate

Run in Latenode’s cloud

Start with an app event. Finish with useful work.

Give every new lead a researched first response.

HubSpot · New Contact

Updated CRM contact + Gmail draft

Answer with the customer’s context already in hand.

Gmail · New Email

Gmail reply draft

Keep the team up to date as new data arrives.

Google Sheets · New Row Added

Slack team update

Turn incoming files into checked records.

Google Drive · New or Modified File

Spreadsheet record + exception notification

Put the context next to the payment alert.

Stripe · New Events

Slack payment alert

Move a new brief toward a reviewable post.

Notion · New Page in Database

Telegram review message

Use AI to build. Spend tokens only where AI is needed.

Add AI where it helps

Set the steps. Or let an agent choose its tools.

A lead follows the steps you set.

An agent chooses the research it needs.

Turn a new contact into a sales-ready brief.

HubSpot · New Contact

Research + qualification

HubSpot update + Gmail draft

See the workflow. Change it by hand or by prompt.

Rule configuration

Follow an app event through every step.

A simpler way to automate customer reports

Execution history

Contact 1042 · Step data

Connect your agent and start building.

Create a Latenode token

Connect your client

Claude Code

Cursor

Other agents

Add the recommended builder skill

Ask for your first workflow