広告掲載
MCP.so
ログイン

n8n AI Agent with Local MCP Integration (Docker + npx)

@s1ds1ngh

リポジトリ

基本情報

カテゴリ

推論

トランスポート

stdio

作者

s1ds1ngh

n8n AI Agent with Local MCP Integration について

概要はまだありません

#n8n#ai-agent#mcp-integration

n8n AI Agent with Local MCP Integration の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "Case-Study-RAG-Workflow-automation-with-n8n-and-gdrive-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-it",
        "--rm",
        "--name",
        "n8n",
        "-p",
        "5678:5678",
        "\\"
      ]
    }
  }
}

n8n AI Agent with Local MCP Integration のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is n8n AI Agent with Local MCP Integration (Docker + npx)?

This repository provides an n8n workflow that integrates the Model Context Protocol (MCP) with a locally run n8n instance via Docker. It enables AI Agents to dynamically discover and use external tools (e.g., web search) by running MCP servers on‑the‑fly with the npx command, removing the need for persistent server installations. It targets n8n users who want to extend their AI Agents with modular, on‑demand tooling.

How to use n8n AI Agent with Local MCP Integration (Docker + npx)?

  1. Start n8n in Docker with the environment variable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true.
  2. Install the community node n8n-nodes-mcp via n8n’s Settings → Community Nodes.
  3. Create an MCP Client credential using Command Line (STDIO), setting the command to npx and the arguments to the desired MCP server (e.g., run -y @modelcontextprotocol/server-brave-search). Add any required API keys as environment variables.
  4. Import the provided workflow JSON, configure the AI Agent’s chat model and memory, and activate the workflow.
  5. Use the n8n chat interface to send queries; the AI Agent will automatically list available MCP tools and execute the appropriate one.

Key features of n8n AI Agent with Local MCP Integration (Docker + npx)

  • On‑demand tool discovery and execution via MCP
  • Uses npx to run MCP servers without permanent installation
  • Runs n8n locally inside a Docker container
  • AI Agent intelligently selects tools based on schema
  • Supports API keys through credential environment variables
  • Easily swap MCP servers by changing the npx command

Use cases of n8n AI Agent with Local MCP Integration (Docker + npx)

  • Enable an AI Agent to perform web searches through Brave Search
  • List all available tools dynamically and let the AI choose one
  • Execute external APIs (e.g., weather, news) without a dedicated server
  • Quickly prototype AI workflows that require ephemeral tooling

よくある質問

1

Why is the `N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE` flag required?

This environment variable lets the AI Agent node treat community nodes (like the MCP Client) as executable tools. Without it, the Agent cannot call the MCP Client operations.

2

How does the `npx` method work for running MCP servers?

`npx` runs Node.js packages from the npm registry without permanently installing them. Inside the MCP Client credential, you set the command to `npx` and provide the server’s package name and arguments. n8n executes this command via STDIO to communicate with the MCP server.

3

What are the system requirements?

Docker must be installed and running on your local machine. Node.js and npm are recommended for troubleshooting and ensuring `npx` is available. You also need a basic understanding of n8n workflows and credentials.

4

Can I use a different MCP server instead of Brave Search?

Yes. Find the `npx` command for any MCP server (e.g., `@modelcontextprotocol/server-everything`) and replace the arguments in the credential. Add any required environment variables (like API keys) as needed.

5

How do I provide API keys for authenticated MCP servers?

In the MCP Client credential, under **Environments**, click **Add Environment Variable**. Enter the exact name required by the MCP server (e.g., `BRAVE_API_KEY`) and your key as the value. The server will receive this variable when launched via `npx`.

コメント

「推論」の他のコンテンツ

Part 1. Real-Time LangGraph Agent with MCP Tool Execution

junfanz1

This project demonstrates a decoupled real-time agent architecture that connects LangGraph agents to remote tools served by custom MCP (Modular Command Protocol) servers. The architecture enables a flexible and scalable multi-agent system where each tool can be hosted independent

27

quarkus-langchain4j-workshop

quarkusio

Quarkus LangChain4J Workshop that demonstrates both single AI service capabilities and Agentic AI orchestration

91

MCP Sandbox

JohanLi233

Python sandboxes for llms

40

Proplan Mcp

King-Proplan

MCP server that gives Claude persistent project memory — roadmap, session history, and codebase context. Type continue and Claude picks up exactly where you left off

5

n8n Workflow Builder MCP

ifmelate

MCP server that allow LLM in agent mode builds n8n workflows for you

51
広告掲載