How to link MCP to foundry using maker authentication/configuration

[DennesTorres]

I'm confused about how to do this, some people told me it's not possible and this makes me confused about why and if I'm with the wrong point of view.

Let me explain in details:

I want to link an MCP to Foundry and test it in playground. It seems simple. There is a reason for this.

I would like to create an agent linked to an MCP in a way to ensure a certain level of encapsulation. The consumers of the agent should not need to know technical internal details about the tools used by the agent.

First question: Am I wrong in trying this? Am I using the wrong point of view?

The problem is that there are information required by the tool - MCP - which can only be provided to the "run" or "thread". There are two information in this case: The authentication and the configuration to run without requiring interruption (otherwise it stops with the error "requires action").

The "run" and "thread" is only created by the consumer, when already starting the execution. This requires the consumer to know internal details about the tools, breaking the encapsulation. (Am I wrong?).

The copilot studio doesn't work in this way. Using copilot studio I have the option to choose if I will use "maker authentication" or a passthrough authentication and this seems very good.

The SDKs, both in Python and C#, allow the authentication and configuration to be sent in the moment of the agent creation, but the information is ignored.

Questions:

Is this something planned for development?

If not, why ?