> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/advanced-ai/mcp/install-community-nodes.md).

# Install verified community nodes with Duaer MCP

In Duaer, a connected MCP client can install a verified community node. The client needs that permission, and it asks you before it installs.
## Turn on Instance-level Duaer first

1. Open Settings → Instance-level Duaer.
2. Enable access, and connect the client from the [connect page](/connect/connect-to-duaer-mcp-server.md).
3. On the connected client, confirm its access includes Install verified community nodes. Without that scope, the client cannot install for you.

## Install, then use the node

1. Ask the client to search nodes. Verified community nodes that are not installed are listed apart from nodes already on the instance.
2. The client should ask before it installs. After you agree, it installs the verified version the registry publishes.
3. Open Settings → Community nodes and confirm the package is there. Only then can the canvas use its nodes and create the credentials they need.

This path installs verified packages only. An unverified community package is not installed from MCP. You can also install a verified package from the nodes panel; it shows up in Community nodes either way. When environment variables manage community packages, that settings page is read-only, as the page itself says.
## Questions

### Can a Duaer MCP client install any community package?

No. In Duaer it can install a verified community node, and only after you agree. An unverified package is not installed on this path.

### Where do installed community nodes show up in Duaer?

Settings → Community nodes. The canvas can use the nodes after the package is listed there.