Mukoko News vs Zapier MCP server
A side-by-side look at the Mukoko News and Zapier MCP server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mukoko News for aggregators work over a hosted endpoint; choose Zapier MCP server for aggregators over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mukoko News when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get_briefing, track_story, get_location_news.
Choose Zapier MCP server when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
search_zapier, query_docs_filesystem_zapier, submit_feedback.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 59/100 · Good | 73/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 447 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | 3 |
| Full listing | View Mukoko News | View Zapier MCP server |
Tools & capabilities
Mukoko News tools 16
get_briefingAnswer "What's happening in [place/topic]?" — top story, recent articles, and trending topics in one call. Accepts country codes (ZW, KE), region names (East Africa, Southern Africa), category topics (politics, business), or omit focus for a pan-African overview. Returns short excerpts with word counts and app links only — call get_article with an article id to read a full article body inline.track_storyFollow the development of a news story over time. Returns articles in chronological order showing how a story evolved. Use since to control the lookback window.get_location_newsNews from a specific place in Africa. Accepts country codes, country names, region names, or city names.compare_locationsCompare news coverage between 2–4 African countries or regions side by side.get_source_viewSee how a specific news source is covering a topic.find_storiesSearch articles by keyword, tag, category, or country. Results carry short excerpts, word counts, and app links only — call get_article with a result's id to read the full article body inline.get_articleRead a single article by ID or slug. Returns the full article body inline as markdown (truncated at ~8000 characters with a link to continue in the app) plus source metadata and the Mukoko app URL. Use this after a list tool (get_briefing, find_stories, …) to read an article without leaving the conversation.list_categoriesList all news categories with article counts.list_sourcesList active news sources. Optionally filter by country code.get_statsPlatform statistics: total articles, active sources, and today's output.get_my_feedPersonalised news feed based on the authenticated user's article likes and saves. Requires Authorization: Bearer <WorkOS access token>.get_trending_analyticsOpen analytics: trending topics, categories, keywords, and sources for any location or period. Part of Mukoko's open data policy.- +4 more on the listing page
Zapier MCP server tools 3
search_zapierSearch across the Zapier knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Zapier, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).query_docs_filesystem_zapierRun a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Zapier documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `cat /openapi/package.json | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted at: `'/openapi/https://api.zapier.com/schema'`, `/openapi/api-reference/specs/agentic-management.yaml`, `/openapi/white-label/actions-openapi.yaml`, `/openapi/api-reference/specs/actions.yaml`, `/openapi/white-label/trigger-inbox-openapi.yaml`, `/openapi/api-reference/specs/trigger-inbox.yaml`, `/openapi/api-reference/specs/connections.yaml`, `/openapi/powered-by-zapier/api-reference/promotions-openapi.yaml`, `/openapi/package.json`, `/openapi/tsconfig.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.submit_feedbackReport a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.
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.
Mukoko News
{
"mcpServers": {
"mukoko-news": {
"url": "https://news.mukoko.dev/mcp"
}
}
}
Zapier MCP server
{
"mcpServers": {
"zapier-mcp-server": {
"url": "https://docs.zapier.com/mcp/home"
}
}
}
Frequently asked questions
Mukoko News is categorized under Aggregators and uses a remote HTTP/SSE transport. Zapier MCP server belongs to Aggregators and uses a remote HTTP/SSE transport. Pick Mukoko News for aggregators work and Zapier MCP server for aggregators.
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.
Mukoko News has no declared pricing — check the project's own site. Zapier MCP server 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 mukoko-news and zapier-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mukoko News has a quality signal of 59/100 (Good) with 3 views, 0 installs and 2 GitHub stars. Zapier MCP server has 73/100 (Great) with 2 views, 0 installs and 447 GitHub stars.