Apify MCP Server vs BetterPost
A side-by-side look at the Apify MCP Server and BetterPost MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Apify MCP Server for search & data extraction work as a local process; choose BetterPost for search & data extraction over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Apify MCP Server when
- You need dedicated capabilities in the Search & Data Extraction 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 BetterPost when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
betterpost_create_project, betterpost_generate_content, betterpost_derive_content.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 68/100 · Great | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | APIFY_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12,907 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 13 | 23 |
| Full listing | View Apify MCP Server | View BetterPost |
Tools & capabilities
Apify MCP Server tools 13
titlereadOnlyHinttrueget-datasetfetch-actor-detailsapify--web-fetchapify--website-content-crawlerpageFunctioninitialCookiesopenWorldHintcall-actorsearch-actors- +1 more on the listing page
BetterPost tools 23
betterpost_create_projectCreate a content project. Slow, one-shot: infers config (criteria, industry, tone), discovers sources, and gathers/ranks an initial set of timely stories. Best called after the inferred audience, description, and tone have been confirmed with the user, since the config shapes everything downstream.betterpost_generate_contentGenerate a new piece of content for a project from its timely, relevant stories. Fast in steady state. Charges credits on success only. If you pass a `topic` the project has no stories about, this returns a `topic_unavailable` error (no charge) carrying an `inScope` flag and next steps — it never silently writes an off-topic piece.betterpost_derive_contentTransform an existing piece into another format (e.g. newsletter → tweet). No fetching; reuses the source stories and topic.betterpost_list_contentList a project's content (summaries + shareable `publicUrl` links).betterpost_get_contentFetch one piece of content in full.betterpost_delete_contentDelete a piece of content and its hosted images.betterpost_list_projectsReturns your projects, each with its relevance `criteria` (with ids) that define what counts as on-topic.betterpost_get_projectReturns one project with its relevance `criteria` (each with an id, so a criterion can be targeted for removal via betterpost_update_project).betterpost_update_projectUpdates a project's title, audience, description, tone, freshness window, timezone, or relevance criteria, and returns the updated project with its criteria. Changing title/audience/description re-derives the relevance criteria (replace-all), which broadens or narrows what counts as on-topic. To edit criteria incrementally instead, pass `patch.addCriteria` (texts to append) and/or `patch.removeCriteria` (criterion ids from get_project/list_projects). Dates default to US Eastern unless a `timezone` (an IANA name like "America/New_York") is set.betterpost_delete_projectPermanently deletes a project and everything in it — its sources, stories, and content. Cannot be undone.betterpost_list_sourcesReturns one slimmed page of a project's sources plus project-wide `total` and `counts` (ok/failing/disabled/pending, and byType). Page with `limit` (default 50) and `offset`, following the returned `nextOffset` until it is null.betterpost_add_sourceAdds a source to a project and fetches it immediately (bounded by a few seconds), returning `storiesAdded` so the next generate_content can use it; if it is still fetching it returns `fetched:false` with a note. Doubles as manual source import: paste any URL (RSS/Atom feed, article, or a page, profile, or post on a supported platform) and leave `type` as autodetect, or create a recurring keyword search by setting `value` to the search terms and `type` to a search kind (see `type`).- +11 more on 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.
Apify MCP Server
{
"mcpServers": {
"apify-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
BetterPost
{
"mcpServers": {
"betterpost": {
"url": "https://betterpost.ai/mcp"
}
}
}
Frequently asked questions
Apify MCP Server is categorized under Search & Data Extraction and uses a local stdio subprocess. BetterPost belongs to Search & Data Extraction and uses a remote HTTP/SSE transport. Pick Apify MCP Server for search & data extraction work and BetterPost for search & data extraction.
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.
Apify MCP Server has no declared pricing — check the project's own site. Auth: oauth 2.0. BetterPost has no declared pricing — check the project's own site. Auth: no auth required. 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-mcp-server and betterpost as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Apify MCP Server has a quality signal of 68/100 (Great) with 6 views, 0 installs and 12,907 GitHub stars. BetterPost has 67/100 (Great) with 1 views, 0 installs and 0 GitHub stars.