Help getting the MCP trigger to pass a variable into an http request tool

[trijste]

I’m trying to build an MCP server that has access to my Salesforce org, but only at the schema and describe object level, ideally to provide more information for building out SOQL queries using custom fields from custom objects.

I am providing the agent that accesses the MCP server with tools for listing the SObjects, but I then want it to be able to access the describe endpoint for the object so as to access its field metadata for use in constructing the query (potentially multiple calls for different object schemas depending on the complexity of the query).

But I’m not sure how to progress. The initial tool for listing the schema is a single endpoint, but the describe endpoint requires that the object name be used in the query itself. I’m using two HTTP request tools and trying to pass an AI-generated variable into the URL of one of them, like sobjects/{{ $fromAI('SObjectName', 'the API name of the object to return schema for') }}/describe/ but that’s not working.

I’m wondering if anyone has done anything similar and can help me figure it out.

[jabbson]

Hey @trijste hope all is good.

When you say “but that’s not working”… would you like to expand on that? What is not working? How is it not working exactly?

Overall it is not clear whether the issue is related to MCP in any way, if so - how, if not,… well, why?

You make the mcp call to get the listing of all objects, and then you make a rest call to SF to get the object description?

[trijste]

Hey @jabbson thanks for taking a look. It’s a basic MCP workflow structure:

While there was nothing in the content of your response that solved this for me, your engagement nevertheless caused me to take a closer, better look at my setup and realize I had the MCP server improperly installed. I uninstalled it and reinstalled it, and it’s now working perfectly.

[jabbson]

Haha, glad to provide support, even if it is just to encourage you to double check your setup. Great job fixing it, @trijste!