How can I access published custom components on the MCP server in Pipedream?

This topic was automatically generated from Slack. You can find the original thread here.

on the hosted MCP server, when publishing custom components, how do we access them? docs say:

Custom actions that you publish are automatically exposed as tools in the Pipedream MCP server for the relevant app.
passing the app name to the MCP server for a tools list call BASE/v1/:extid/:app , none of these work:
• app = ~ (as per doc)
• app = ~/
• app = the prefix for my component (where I have followed naming conventions, app-someactionname )

some output ID I got from the pd publish if helpful:
sc_1LiRMQwg

I am reusing the google_calendar helpers that supply the app prop (doc) so I believe this should be on google_calendar

I’ve published to both development and production and tried querying both (through the x-pd-environment header bc the environment header values appear to be borked for dev on the python sdk?)

I have not gotten this to work but I’m just gonna go with pure Actions instead of using the MCP server, since I do see my custom Action in that API response

maybe it has something to do with the fact that the pipedream sdk version is 1.5.4 in the MCP repo, and the current is 1.7.0?

The SDK vers could potentially be an issue? But the app should indeed be something like google_calendar for example. What app did you publish custom tools for?

The core issue is that you’re not able to list the tools you published?

If you’re using the hosted MCP server can you just use the latest SDK version?

Or use the remote MCP server instead? What’s the core use case for self hosting?

• yes, the app was google_calendar

The core issue is that you’re not able to list the tools you published
yep ^ for the app google_calendar

I was using the remote MCP server. for some reason, when I tried to reproduce this underlying SDK call by doing an actions.list on the latest (Python) SDK version, it worked as intended. so I’m all good now!