Actors MCP Server vs Cellarion
A side-by-side look at the Actors MCP Server and Cellarion MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Actors MCP Server for other tools and integrations work as a local process; choose Cellarion for other tools and integrations over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Actors MCP Server when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
APIFY_TOKEN. - You want tools like
title, readOnlyHint, true.
Choose Cellarion when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
JWT_SECRET, MEILI_MASTER_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Other Tools and Integrations |
| Quality signal | 68/100 · Great | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | APIFY_TOKEN | JWT_SECRETMEILI_MASTER_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12,759 | 26 |
| Directory activity | 7 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 13 | Not listed |
| Full listing | View Actors MCP Server | View Cellarion |
Tools & capabilities
Actors MCP Server tools 13
titlereadOnlyHinttrueget-datasetfetch-actor-detailsapify--web-fetchapify--website-content-crawlerpageFunctioninitialCookiesopenWorldHintcall-actorsearch-actors- +1 more on the listing page
Cellarion tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Actors MCP Server
{
"mcpServers": {
"apify-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
Cellarion
{
"mcpServers": {
"cellarion": {
"url": "https://cellarion.app/api/mcp"
}
}
}
Frequently asked questions
Actors MCP Server is categorized under Other Tools and Integrations and uses a local stdio subprocess. Cellarion belongs to Other Tools and Integrations and uses a remote HTTP/SSE transport. Pick Actors MCP Server for other tools and integrations work and Cellarion for other tools and integrations.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Actors MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. Cellarion has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add apify-actors-mcp-server and cellarion as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Actors MCP Server has a quality signal of 68/100 (Great) with 7 views, 0 installs and 12,759 GitHub stars. Cellarion has 44/100 (Fair) with 2 views, 0 installs and 26 GitHub stars.