---
title: n8n Cloud
description: Use Veefore from n8n Cloud today through the MCP Client Tool, and with the Veefore node once it is verified.
---
n8n Cloud installs only **verified** community nodes. Until the Veefore node is
verified (see [Publish the n8n node](/build/publish-n8n-node)), n8n Cloud uses
Veefore through n8n's built-in **MCP Client Tool**, on an AI Agent.

Do the [shared setup](/build/connect-agents) first.

## Step by step

:::steps
:::step Create an MCP key
**Agents → your n8n agent → MCP keys → Create**. Copy the `vf_mcp_…` key.
:::
:::step Register the runtime
**Integrations → n8n — customer-owned → Add**, your instance URL
(`https://<name>.app.n8n.cloud`) and the agent.

Optionally add an n8n API key so Veefore can inspect your workflows: in n8n,
**Settings → n8n API → Create an API key** with the scopes `workflow:list`,
`workflow:read`, `credential:list`, `user:list` and `securityAudit:generate`.
Then **Verify now** on the runtime page.
:::
:::step Add the credential in n8n
**Credentials → New → Header Auth**: name `Authorization`, value
`Bearer vf_mcp_…`.
:::
:::step Add the tool to your AI Agent
On the AI Agent node, **Tools → + → MCP Client Tool**:

| Field | Value |
| --- | --- |
| Endpoint | `https://gateway.veefore.com/mcp` |
| Server Transport | HTTP Streamable |
| Authentication | Header Auth, the credential from step 3 |
| Tools to include | All |
:::
:::step Remove direct tools
Disconnect any Gmail, Slack, HTTP Request or Code tool that performs the same
actions. Otherwise the model can choose them instead, and Veefore never sees the
call. The verifier reports them as `AI_TOOL_BYPASS`.
:::
:::step Try it
Chat with the agent: *"Send ops@example.com a test email."* It calls
`veefore_authorize`, then `veefore_execute`. Check **Actions** in the console.
:::
:::

The tools are the same as for Claude; see [the tool list](/build/claude#the-tools).

## Limits of this route

- Only the AI Agent can use it. A plain workflow step (not an agent) needs the
  Veefore node.
- It is not the Veefore node, so the audit trail does not carry the n8n
  workflow and execution ids.
- Anyone who can edit the workflow can still add a direct node. Register the
  instance with an API key so verification finds it.

When the Veefore node is verified, install it from the nodes panel (search
**Veefore**) and follow [n8n (self-hosted)](/build/n8n) from *Add the
credential* onward; the steps are the same.