n8n-nodes-onepage-mcp

An n8n Community Node that exposes the OnePage MCP server to your AI Agent – every OnePage tool, with its own input schema, over the Model Context Protocol.

Looking for the OnePage Trigger (real-time new-lead webhook)? That node lives in its own package: n8n-nodes-onepage.

What is n8n?

n8n is a workflow automation tool that lets you automate processes between different web applications – such as OnePage, CRM systems, Slack, email, or databases.

Instead of manual work, processes run automatically in the background as soon as an event occurs.

⚖️ Legal Notice

This community node uses the public OnePage MCP server and is not officially affiliated with OnePage.

All trademarks and product names are the property of their respective owners.

Note: This is a community-developed integration. For official support, please contact OnePage directly.

🤖 Overview

The Onepage MCP node is an AI Agent tool sub-node: attach it to the Tools input of an n8n AI Agent and it exposes all tools of the Onepage MCP server (https://mcp.onepage.io/) to the agent — each as its own tool with its own input schema. Tool calls are forwarded to the MCP server via the Model Context Protocol (Streamable HTTP). Authentication uses OAuth 2.1 (no manual API key).

It can only be used as an AI tool — it has no main workflow input/output. Optionally restrict which tools the agent sees via Tools to Expose (All / Selected / All Except), and set a Timeout under Options.

The agent sees each tool as <NodeName>_<mcpToolName> (for example Onepage_MCP_list_pages), so two MCP tool nodes on the same agent never collide. Calls are always forwarded to the MCP server under the tool's original name. All tool calls of one workflow execution share a single MCP session.

📦 Installation

Requirements

• n8n 2.32.0 or newer (or the 2.30.8 / 2.31.5 patch releases). Older versions cannot read a tool collection supplied by a community node, because n8n-core only started matching it structurally in those releases — the node would connect but the agent would see no tools.

• Active OnePage account.

• Self-hosted n8n: community tool nodes must be enabled via the environment variable:

  N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true

Installation via Community Nodes

1. Open your n8n instance

2. Go to Settings → Community Nodes

3. Click Install

4. Install one of the following packages:

Option 1 – Scoped (recommended)

@rjsebening/n8n-nodes-onepage-mcp

Option 2 – Unscoped

n8n-nodes-onepage-mcp

5. Restart n8n → Node is available

🔐 Configuration

Authentication uses an Onepage MCP OAuth2 API credential (OAuth 2.1 / PKCE, automatic discovery and Dynamic Client Registration). There is nothing to fill in — no Client ID, no server URL.

1. Add the Onepage MCP node to a workflow and open it.
2. Click Connect, log in on the Onepage login page and approve.
3. Done — n8n discovers the endpoints, registers a client, and stores the tokens.

Full details, including token lifetime and when a manual reconnect is needed: CREDENTIALS.md.

🧩 Example workflow

1. Add an AI Agent node and a Chat Model.
2. Add the Onepage MCP node and connect it to the agent's Tools input.
3. Select your Onepage MCP OAuth2 API credential on the node.
4. Ask the agent a question that needs Onepage data — it sees and calls every Onepage MCP tool.

📖 Typical Use Cases

• Let an agent answer questions about your OnePage pages, forms and leads
• Automated research and reporting across your OnePage data
• Assistants that create or update OnePage content on request
• Combine OnePage tools with other MCP servers on the same agent

📬 About the author

I am Rezk Jörg Sebening – a business automation expert for n8n, APIs, and scalable processes in the DACH region.

I develop n8n nodes and systems that consistently eliminate manual work.

👉 Follow me on GitHub for more practical community nodes and integrations.

📋 Disclaimer

This unofficial community Node is not affiliated with, supported, or sponsored by OnePage.
It only provides an interface to the publicly available OnePage MCP server under its terms of use.

Important Notes:

• This Node is developed and maintained by the community
• For issues with the OnePage MCP server itself, please contact official OnePage support
• All OnePage trademarks and logos belong to OnePage
• This Node only acts as a connector to the public MCP server