Building and monetizing MCP servers on Apify
Learn how to turn MCP servers into revenue with our webinar on July 3, 11 am EST (5 pm CET), hosted by our experts.
Publish your MCP server on Apify
This technical webinar will teach you how to deploy MCP servers on the Apify platform and implement pay-per-event monetization to generate revenue, without having to manage any infrastructure.
Speakers
The webinar will feature Jakub Kopecky, AI Engineer at Apify, Sameh Jarour, Senior Product Marketing Manager at Apify, and Dušan Vystrčil, Product Manager for AI at Apify, and Federico Ulfo, Founder at FlowAI.
What will be covered in the webinar?
MCP server deployment fundamentals
Learn all about how to build and deploy MCP servers on the Apify platform. We’ll cover the differences between transport protocols and explore the benefits of Apify's infrastructure. We’ll also explain how pay-per-event billing integrates directly into your server code.
Paths to MCP server creation
We’ll demo and explore various approaches to building MCP servers based on existing code. We’ll show live demonstrations of code-first development using our Python and TypeScript templates, as well as API-based creation of existing servers.
Revenue generation and production optimization
We’ll go over everything you need to know about the business aspect of MCP server deployment. Learn all about pay-per-event pricing, from how it works, to how you can track usage analytics, to the different strategies open to you.
Production deployment best practices
We’ll introduce live demos with developers and other agent platforms to showcase how they’ve built their servers and examine the revenue potential of MCP servers in the industry.
No. We’ll show you how to build MCP servers from scratch using templates or convert existing APIs.
Basic familiarity with APIs and either Python, TypeScript, or visual workflow tools. We’ll provide templates and step-by-step guidance.
PPE billing involves you defining specific processes and events in the use of your MCP server (tool executions, API calls, data processing) and setting pricing. Apify handles payment processing and provides analytics on usage and revenue.
Apify charges based on compute usage. With standby mode, idle servers use minimal resources and scale automatically when requests arrive.
You can distribute servers through Apify Store for public distribution, or private deployment for internal or client-specific use cases. Both support the same billing and scaling features.
Yes. Local development typically uses stdio transport for testing with Claude Desktop. Cloud deployment uses SSE endpoints that work with any MCP client and support multiple concurrent users.