MCP HTTP request and Pieces Actions

[Bram]

HI Team @Gamal,

I’ve set-up my first MCP with Claude, first results look amazing, I was able to send an email via Claude.

1. In the MCP(ieces) ;), I noticed there is only one HTTP option for Oauth2, I think the HTTP is connected by default? Is that correct? It looks like now to make use of the HTTP piece we would have to share our API key, or am I overlooking something?

2. In order to use the pieces to there full potential, is it necessary to have the actions available for each piece? or can we use the Custom API option too? And what if the Custom API call is not available for those pieces?

Looking forward to the clarification!

KR Bram

[Abdul]

Could you further elaborate on what you mean on the first questoin Bram, like what is the oauth2 you are talking about ?

You can use the Custom API request action, you would have to send it the schema you would as if you are using it in the flow.

Here is a screenshot from Cursor for this:

[Bram]

Hi Abdul,

Thanks for your quick response!

1. when trying to connect a new Piece
   
   
   
   All I can see here is the the (Oauth2), but it seems the Http request is installed by default ‘custom_api_call’ as a general piece or is this piece related? (btw I thought this morning it was named HTTP request, maybe updated in the mean time…)

2. Please see the piece of Flowlu Flowlu · Activepieces and VBOUT VBOUT · Activepieces i.e. they do not have the ‘Custom API call’ option available, if they would have that too I would no be having to use a general custom API call action.

The one you see in the Screenshot above is probably the one from the Gmail piece I connected.

I hope this clarifies a bit more, if not please let me know!

KR Bram

[Abdul]

Hi there @Bram, the piece you see is related to a feature we created for OAuth2 connections, the default HTTP piece doesn’t have connections and it is not showing, we will be working on making it available soon.

In regards to you second question for the custom_api_call, it uses the same schema you see here

It’s basically the same as what you have in the UI.

[Bram]

Hi @Abdul,

Thanks, understanding the first 1.

For the custom API call, I think it’s important that it’s set-up for the piece within AP otherwise it can’t be used for the MCP, correct?

The Flowlu piece and the VBOUT piece both do not have a custom API call option within their actions in AP. Please see the previous shared links for those pieces. I assume to use them the Custom API Call action should be available right?