I’m trying to use the documented path parameter mechanism in MCP Servers:
I have been able to establish a parameter based path using the following as my path:
“/:$MCP_ID”
This resolves when I connect to my MCP server from an AI Agent. I can select tools and I’m able to use the MCP server. But I am unable to retrieve my MCP_ID parameter value.
No error, just not able to use my parameter value from my MCP Server tool.
Follow up question… are the variables usable in MCP Server paths the environment variables that are only available from a Pro or Enterprise plan?
Is no one else trying to do this?
I also would like to find a way to do that.
Is there any way to send parameters from an AI agent to its MCP Client, to the MCP server and finally to the MCP tool?
From what I’m experiencing, MCP Server/Client do not support sending or receiving parameters.
You can (do that) by the way.
@cutecatcode would you be able to provide the steps to make this work? The n8n documentation on it is severely lacking in implementation information. Would really appreciate any info you can provide :).
Okay, I will give you a sample and steps to make the each MCP communicate.
If it helps you to understand, kindly mark my message as solution, thanks!
Hey @cutecatcode thanks for your input :). Unfortunately I’m already at this point. I’ve got lots of MCP servers stood up and I can use them. The problem is when I try to use the Path feature in the MCP Server trigger, it does not work. I can define a path parameter, and when I use my MCP server it only works if my path includes a parameter value. But the value is not available to me in my MCP Server workflow.
Have you tried to use the Path parameter feature? Thanks!