What is the Pricing for Using Managed OAuth with MCP Server in a MacOS App with 1000 Users and 5 Connected Services?

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

Could someone please help me understand the pricing for oauth relating to the MCP server? For more context I am working on a macOS app where users can chat with an LLM, and I have added support for the Pipedream MCP server, and each user would thus be authenticating to individual services using the managed oauth solution. How would the billing/pricing look like for my use case. For example if I have 1000 users each with 5 connected services (i.e gmail, slack, notion e.t.c), each using the managed oauth.

That would count as 1000 users

Hi I had a follow-up question related to this. We also have an app where we allow users to select tools/actions from Pipedream MCPs. Now just for testing we want to allow them to use a tool in free plan. This is a problem for us because even at 1000 free users, our bill becomes ~2k USD.

Is it possible to have a trail period for external users because it would be a challenge to convert them without having them test the tools.

I was thinking of removing the UserID from pipedream after our products trail period. How would that work at your end? Please let me know if we can do something about this issue as I think its a big problem for all Dev customers you have/will get.

We only charge for active users (those for whom you make API requests / tool calls), so if they try your product once and never come back, those won’t be charged as active users.

We are exploring the idea for more explicit “free” users though, where they’d maybe just have lower rate limits or shorter life spans and get deleted automatically or something, but that’s a bit farther off, development-wise.

OKay, thanks for the insight. We plan to allow them use the tools just for that session within the app (no deployment). And we will delete the userID from your servers right after the session.

Looking forward to more development updates on this and better guidelines if we have at some point. Thanks for your response.