My MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@My MCP Serverlist available tools"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server template
A template for running and monetizing a Model Context Protocol server using stdio transport on Apify platform. This allows you to run any stdio MCP server as a standby Actor and connect via either the streamable HTTP transport with an MCP client.
Note: the check_dependency_tree_risk tool only scans the first 100 packages found in a package-lock.json and only returns details for Medium-severity-or-above findings, to keep results bounded on very large dependency trees.
Related MCP server: Paid MCP Server Template
How to use
Change the MCP_COMMAND to spawn your stdio MCP server in src/main.ts, and don't forget to install the required MCP server in the package.json (using npm install ...).
By default, this template runs an Everything MCP Server using the following command:
const MCP_COMMAND = [
'npx',
'@modelcontextprotocol/server-everything',
];Alternatively, you can use the mcp-remote tool to turn a remote MCP server into an Actor. For example, to connect to a remote server with authentication:
const MCP_COMMAND = [
'npx',
'mcp-remote',
'https://mcp.apify.com',
'--header',
'Authorization: Bearer TOKEN',
];Feel free to configure billing logic in .actor/pay_per_event.json and src/billing.ts.
Push your Actor to the Apify platform, configure standby mode, and then connect to the Actor standby URL with your MCP client using the endpoint: https://me--my-mcp-server.apify.actor/mcp (streamable HTTP transport).
Important: When connecting to your deployed MCP server, you must pass your Apify API token in the Authorization header as a Bearer token. For example:
Authorization: Bearer <YOUR_APIFY_API_TOKEN>This is required for authentication and to access your Actor endpoint.
Pay per event
This template uses the Pay Per Event (PPE) monetization model, which provides flexible pricing based on defined events.
To charge users, define events in JSON format and save them on the Apify platform. Here is an example schema with the tool-request event:
[
{
"tool-request": {
"eventTitle": "Price for completing a tool request",
"eventDescription": "Flat fee for completing a tool request.",
"eventPriceUsd": 0.05
}
}
]In the Actor, trigger the event with:
await Actor.charge({ eventName: 'tool-request' });This approach allows you to programmatically charge users directly from your Actor, covering the costs of execution and related services.
To set up the PPE model for this Actor:
Configure Pay Per Event: establish the Pay Per Event pricing schema in the Actor's Monetization settings. First, set the Pricing model to
Pay per eventand add the schema. An example schema can be found in pay_per_event.json.
Resources
Getting started
For complete information see this article. To run the Actor use the following command:
apify runDeploy to Apify
Connect Git repository to Apify
If you've created a Git repository for the project, you can easily connect to Apify:
Go to Actor creation page
Click on Link Git Repository button
Push project on your local machine to Apify
You can also deploy the project on your local machine to Apify without the need for the Git repository.
Log in to Apify. You will need to provide your Apify API Token to complete this action.
apify loginDeploy your Actor. This command will deploy and build the Actor on the Apify Platform. You can find your newly created Actor under Actors -> My Actors.
apify push
Documentation reference
To learn more about Apify and Actors, take a look at the following resources:
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceA template for creating and deploying Model Context Protocol servers on the Apify platform using FastMCP, with built-in support for pay-per-event monetization and standby mode hosting.Last updated
- Flicense-qualityDmaintenanceA production-ready template for building monetized MCP servers that require per-call payments via the Mainlayer infrastructure. It provides a structured payment gate that ensures AI agents pay for tool usage before accessing server logic or data.Last updated
- Alicense-qualityCmaintenanceTemplate for creating MCP servers with a server-side paywall gate, enabling free local usage and premium hosted tier with Stripe and x402 payment lanes.Last updatedMIT
- Alicense-qualityCmaintenanceA template for MCP servers that enforces a paywall gate, offering free local execution and monetizing premium features via Stripe or x402 payments.Last updatedMIT
Related MCP Connectors
An MCP server for Arcjet - the runtime security platform that ships with your AI code.
MCP (Model Context Protocol) server for Appwrite
Primarily to be used as a template repository for developing MCP servers with FastMCP in Python, P…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/czcz0009/my-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server