Latenode MCP Server
Model Context Protocol (MCP) is a standard way for AI tools to call external apps. The Latenode MCP Server exposes your workspace to MCP clients such as Cursor, Claude Desktop, and Codex CLI. Instead of building on the canvas yourself, you describe the scenario in the client you already use, and the agent creates or updates it in Latenode.
Think of it as pair-programming for automations: the agent has tools to search node types, create scenarios, run executions, and manage connections.
When to choose MCP
- You spend most of your day in an IDE or AI chat, not in the browser builder.
- You want to script or automate scenario creation from an agent.
- You are building many similar scenarios and prefer natural language over repeated clicking.
- You already use MCP for other tools and want Latenode in the same stack.
What the agent can do
Once connected, a client can call tools such as:
- create_scenario and update_scenario - build or replace nodes on the canvas
- search_node_types - find the right integration or core node
- run_scenario and get_execution - test and inspect runs
- list_connections - see which authorizations exist in the workspace
See the full list in MCP Server tools.
Set up in brief
Create an API token
Open app.latenode.com/mcp, click Create Token, set a name and expiry, and copy the token. It is shown only once.
Add the server to your client
Server URL:
https://api.latenode.com/latenode-mcp/v1/mcpUse the token as a Bearer token in the Authorization header (exact steps depend on the client).
Install the scenario builder skill (recommended)
For better node selection and parameter filling, add the latenode-scenario-builder skill alongside MCP. Instructions are on MCP Server overview.
Describe the scenario in chat
Ask the agent to create or update a scenario. Review the result in the Latenode UI, test, and deploy like any manual build.
Supported clients
Setup tabs on the overview page cover Cursor, Claude Desktop, Claude Code, VS Code, and Codex. Any MCP-compatible client that supports HTTP transport and Bearer auth can use the same URL and token.
MCP Server vs MCP Trigger
These solve opposite directions:
- MCP Server (this page): an external agent builds scenarios inside Latenode.
- MCP Trigger (MCP Nodes): your Latenode scenario exposes tools to external clients (for example, a custom API your agent calls).
Go deeper
- MCP Server overview - token, clients, skill install
- MCP Server tools - parameters and responses
- Connecting to MCP Tools - publish your own scenario as MCP tools
AI scenario helper
Describe the task in chat; the assistant proposes a plan and builds the scenario on the canvas.
Template gallery
Copy a ready-made scenario from the gallery and adjust authorizations and settings.
Need Help? Ask the community
If something on this page is missing or unclear, post on the Latenode community forum. Our team and other users usually reply quickly.