Using MCP servers in n8n workflows you sell

Yes, a workflow that calls MCP servers sells here. Sigrix imports it like any other n8n workflow, and the listing tells the buyer what it needs: each MCP server the workflow calls, the tools it uses, and the credentials each one takes. The address of your own server never ships, and the buyer connects theirs.

§ 01 Pick the node for the job

n8n reaches MCP servers through a handful of nodes, and the one you pick decides how the workflow behaves:

• MCP Client runs one tool from a server as an ordinary step. Use it when the workflow always calls the same tool at the same point: look the order up, then open the ticket.
• MCP Client Tool gives a server's tools to an AI Agent node, which decides which to call and when. Use it when the steps depend on what each request says.
• Nodes from n8n's MCP registry, Notion for one, are ready-made connections to well-known servers. n8n knows where those servers live, and whoever runs the workflow signs in with their own account.
• MCP Server Trigger works the other way round: it serves the workflow's own tools to MCP clients such as Claude or Cursor.

A fixed step is cheaper to run and easier to support. Reach for an agent when the order of the steps really changes from one request to the next.

§ 02 What happens to your server's address

A hosted MCP server's address often carries its key in the path, so Sigrix treats the address as a credential. In every copy of the workflow a buyer downloads:

• the address in an MCP Client or MCP Client Tool node is replaced with <YOUR_MCP_SERVER_URL>;
• an address written as an n8n expression with no URL in it, such as ={{ $env.MCP_URL }}, stays as it is, because it holds nothing secret;
• a registry node keeps its address, which is n8n's public one rather than yours;
• an MCP Server Trigger's path is replaced with <YOUR_MCP_PATH>.

Your credentials never ship either. The workflow keeps only which kind of credential each node expects, and the buyer creates their own in their n8n.

§ 03 What the buyer sees before paying

The listing's "What you run, and what it costs you" section is built from the workflow when you import it:

• Services you bring names each MCP server, by its host or, for a registry node, by name, with the tools the workflow uses: all of them, all but a few, or a named list.
• Credentials you provide lists an MCP server URL for each server reached through MCP Client or MCP Client Tool, and that server's own sign-in: a bearer token, a header or an OAuth connection.
• A workflow with an MCP Server Trigger says so in its summary, and when the trigger asks for authentication, the credential its MCP clients present is listed too.
• How it connects draws each MCP step with its server's host.

The buyer imports the workflow into their own n8n, fills in their own addresses and credentials, and runs it. Nothing on Sigrix runs the workflow or the servers.

§ 04 Before you submit

• Run the workflow end to end in your own n8n, against the MCP servers it uses.
• Say in the description what each server is for, and link its setup guide when the buyer has to host it themselves.
• Where you can, give an agent a named list of tools rather than all of them: a shorter list is easier for a buyer to trust.
• Read the listing as a buyer would. Every server and credential the workflow needs should be in it.

A moderator reads every listing before it goes live.

FAQ

Can I sell an n8n workflow that calls MCP servers? Yes. It is imported like any other n8n workflow. The listing names each MCP server the workflow calls and the tools it uses, and the buyer connects their own server.

Does my MCP server's address ship with the workflow? No. The address in an MCP Client or MCP Client Tool node is replaced with <YOUR_MCP_SERVER_URL>, and the buyer adds their own. Only nodes from n8n's own MCP registry keep an address, and it is n8n's public one.

What does a buyer need to run a workflow that calls MCP servers? Their own n8n, access to each MCP server the workflow calls, and that server's credentials. The listing names every server and credential before they buy.

Should I use MCP Client or MCP Client Tool? MCP Client when the workflow always calls the same tool at the same step, and MCP Client Tool when an AI Agent node should decide which tools to call.

Ready to list one? Read how selling n8n workflows works on Sigrix, see what buyers browse in n8n workflows on the marketplace, or find them among products.