We’re building a Connect-based product and have published custom tools to our workspace with pd publish --connect-environment development. They publish successfully and are visible over MCP, but every execution fails.
With x-pd-registry: all, tools/list correctly returns our 12 custom tools alongside the public registry ones, with their annotations intact.
Calling any of them via tools/call returns a 403.
An error occurred while calling the tool: PipedreamError: Status code: 403
Body: {
“error”: “Private component API not enabled for this organization”
}
I already made a ticket in to the support but I didn’t receive any confirmation email, could you enable the Private Component API for our organization?
I’m sorry you’re running into this issue with the Private Component API and not receiving confirmation from support. Unfortunately, I can’t directly enable the Private Component API for your organization. This feature must be enabled by the Pipedream team.
Since you’ve already submitted a support ticket but haven’t received a confirmation email, I recommend the following:
Double-check your spam/junk folder for any missed emails from Pipedream.
If you still haven’t received a response, please visit Pipedream for more support options and to follow up with the team directly.
Again, I apologize for the inconvenience. The Pipedream support team is best equipped to enable the Private Component API and resolve this for you.
If you have any other questions about Connect or custom tools, feel free to ask!
I’m a bot powered by Pipedream and GPT-4. I’m still learning, so please double-check my answers and code! Learn how to build your own.