Google Keep vs MediaWiki MCP Server
A side-by-side look at the Google Keep and MediaWiki 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 Google Keep for knowledge & memory work over a hosted endpoint; choose MediaWiki MCP Server for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Keep when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
keep_list_accounts, keep_find, keep_get_note.
Choose MediaWiki MCP Server when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CONFIG, MCP_TRANSPORT, MCP_LOG_LEVEL. - You want tools like
get-page, get-pages, get-page-history.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | CONFIGMCP_TRANSPORTMCP_LOG_LEVEL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 140 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 30 | 30 |
| Full listing | View Google Keep | View MediaWiki MCP Server |
Tools & capabilities
Google Keep tools 30
keep_list_accountsLista as contas Google Keep vinculadas a este install (id/email, label). Use pra descobrir o `account` quando há várias.keep_findBusca notas no Google Keep. Filtros opcionais: query (título/texto), labels, colors, pinned, archived, trashed (default false).keep_get_noteRetorna uma nota (ou lista) do Google Keep pelo id. Bulk support: accepts note_ids for batched execution.keep_create_noteCria uma nota de texto no Google Keep. Recebe a label 'keep-mcp' automaticamente pra poder ser gerida depois.keep_create_listCria uma checklist no Google Keep. `items` = array de { text, checked }. Recebe a label 'keep-mcp' automaticamente.keep_update_noteAtualiza título e/ou texto de uma nota. Pra listas, edite os itens com os tools de list item. Bulk support: accepts note_ids for batched execution.keep_pin_noteFixa ou desafixa uma nota (`pinned`, default true). Bulk support: accepts note_ids for batched execution.keep_archive_noteArquiva ou desarquiva uma nota (`archived`, default true). Bulk support: accepts note_ids for batched execution.keep_set_note_colorDefine a cor de uma nota. Uma de: DEFAULT, RED, ORANGE, YELLOW, GREEN, TEAL, BLUE, CERULEAN, PURPLE, PINK, BROWN, GRAY. Bulk support: accepts note_ids for batched execution.keep_trash_noteMove uma nota pra lixeira. Bulk support: accepts note_ids for batched execution.keep_restore_noteRestaura uma nota da lixeira. Bulk support: accepts note_ids for batched execution.keep_delete_noteApaga uma nota permanentemente (não dá pra desfazer). Bulk support: accepts note_ids for batched execution.- +18 more on the listing page
MediaWiki MCP Server tools 30
get-pageReturns a single wiki page (wikitext source, rendered HTML, or metadata only). If the title does not exist, an error is returned. Use metadata=true to retrieve the revision ID (for edit-conflict detection), page size, and section outline. Set content="none" to fetch only metadata. Large content is truncated at 75000 bytes by default, with a marker reporting how much of it was returned and which sections a narrower read can target; a follow-up call with section=N fetches a specific section. For more than one page at a time, use get-pages. For a specific historical revision, use get-revision.get-pagesReturns multiple wiki pages in one call (wikitext source or metadata only). Suited to reading a cluster of related pages, diffing a page family, or syncing pages to local storage. Accepts up to 50 titles; missing pages are reported inline (not as errors). One byte budget covers the whole response, 75000 bytes by default: pages come back whole in the order asked for until it is spent, and the pages past that point are named rather than returned, so a follow-up call for those names fetches the rest. Only a first page larger than the budget on its own is truncated, with a marker reporting how much of it was returned and which sections a narrower read can target. For a single page or HTML output, use get-page. requestedTitle is included only when it differs from the resolved title.get-page-historyReturns revision metadata (revision ID, timestamp, user, comment, size, minor flag) for a wiki page, in segments of 20 revisions, newest first. Paginate with olderThan or newerThan (mutually exclusive). If the title does not exist, an error is returned. Boolean flags appear only when true.get-recent-changesReturns recent change events, newest first, in segments of 50. Defaults to edits and page creations; set types to include log actions, categorizations, or external changes. Each row includes title, timestamp, user, revision IDs, size change, flags (minor/bot/new/anon), tags, and change type. Filter by timestamp window, namespaces, user, change tag, or hide flags (hideBots/hideMinor/hideAnon/hideRedirects/hidePatrolled). Pass showPatrolStatus to include per-row patrol state (requires patrol rights). Paginate with the continue token from the truncation marker. For a single page's revision history, use get-page-history. Boolean flags appear only when true; rows report the size delta, not raw old/new lengths.search-pageSearches wiki page titles and page content (full-text) for the provided terms. Returns matching pages with a snippet, size, timestamp, and the namespace the match came from. Covers the namespaces the wiki counts as content unless namespaces names the namespace IDs to search; get-site-info lists a wiki's namespaces and flags which of them hold content. Accepts up to 100 matches per call (default 10); additional matches beyond the cap are flagged in the response — narrow the query to surface more. For title-prefix lookup (e.g. autocomplete), use search-page-by-prefix.search-page-by-prefixReturns wiki page titles beginning with a given prefix (suited to autocomplete and title lookup). Only titles are returned — no snippets, sizes, or IDs. Accepts up to 500 titles per call (default 10); additional matches beyond the cap are flagged in the response. For full-text content search, use search-page.parse-wikitextRenders wikitext through the live wiki without saving. Returns HTML, parse warnings, categories, wikilinks, templates, external URLs, and display title. Suited to dry-running a planned edit before create-page or update-page, or previewing standalone wikitext (template combinations, sanitizer checks) with no target page. HTML output is truncated at 75000 bytes by default, with a marker reporting how much of it was returned; a smaller wikitext fragment in a follow-up call returns the rest.compare-pagesReturns the changes between two versions of a wiki page as a compact text diff. Each side accepts a revision ID, page title (latest revision), or supplied wikitext; text-vs-text is rejected. Only the changes are returned over the wire. For the full text of both sides, fetch with get-page instead. If a title or revision ID does not exist, an error is returned. Set includeDiff=false for a cheap change-detection response that skips diff rendering and returns just the change flag, revision metadata, and size delta. Diff output is truncated at 75000 bytes by default, with a marker reporting how much of it was returned; a narrower revision range or includeDiff=false avoids truncation.get-fileReturns metadata for a file (uploader, timestamp, size, MIME type) along with download URLs for the thumbnail, preview, and original. The File: prefix is added automatically if omitted.get-file-dataFetches a wiki file server-side and returns the image inline as a content block, for clients that cannot reach the wiki host (sandboxed or network-restricted) and need the image sent to the model for visual analysis. Returns a scaled rendition sized by width. Files MediaWiki can rasterize (images, SVG, PDF, DjVu) come back as an image; other types (audio, video, arbitrary binaries) error — for those, and for metadata or a download URL, use get-file.get-revisionReturns a specific historical revision of a wiki page by revision ID (wikitext source, rendered HTML, or metadata only). If the revision ID does not exist, an error is returned. Content is truncated at 75000 bytes by default; a past revision has no narrower read, so for a large one use compare-pages to see what changed. For the latest revision plus metadata, use get-page with metadata=true.get-site-infoReturns key facts about the targeted wiki from its MediaWiki siteinfo: general settings (sitename, MediaWiki version, content language, page-title case-sensitivity, live read-only state, and maxarticlesize in bytes), the namespace map with localized names and aliases, the list of installed extension names, and the content license. Set includeStatistics to also return page, article, edit, image, user, active-user, and admin counts.- +18 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.
Google Keep
{
"mcpServers": {
"google-keep": {
"url": "https://api.mcp.ai/p_keep"
}
}
}
MediaWiki MCP Server
{
"mcpServers": {
"mediawiki-mcp-server": {
"command": "npx",
"args": [
"-y",
"@professional-wiki/mediawiki-mcp-server@latest"
],
"env": {
"CONFIG": "YOUR_CONFIG_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"MCP_LOG_LEVEL": "YOUR_MCP_LOG_LEVEL_HERE"
}
}
}
}
Frequently asked questions
Google Keep is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. MediaWiki MCP Server belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Google Keep for knowledge & memory work and MediaWiki MCP Server for knowledge & memory.
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.
Google Keep has no declared pricing — check the project's own site. MediaWiki MCP Server is listed as free. 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 google-keep and mediawiki-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Keep has a quality signal of 57/100 (Good) with 0 views, 0 installs and 1 GitHub stars. MediaWiki MCP Server has 69/100 (Great) with 4 views, 0 installs and 140 GitHub stars.