MediaWiki MCP Server vs Picorn MCP
A side-by-side look at the MediaWiki MCP Server and Picorn MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MediaWiki MCP Server for developer tools work as a local process; choose Picorn MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MediaWiki MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CONFIG, MCP_TRANSPORT, MCP_LOG_LEVEL, MCP_CONTENT_MAX_BYTES. - You want tools like
get-page, get-pages, get-page-history.
Choose Picorn MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
picorn_capabilities, picorn_projects_create, picorn_projects_inspect.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 68/100 · Great | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | CONFIGMCP_TRANSPORTMCP_LOG_LEVELMCP_CONTENT_MAX_BYTES |
Tools & capabilities
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.
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.
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",
"MCP_CONTENT_MAX_BYTES": "YOUR_MCP_CONTENT_MAX_BYTES_HERE"
}
}
}
}
Picorn MCP
{
"mcpServers": {
"picorn-mcp": {
"url": "https://picorn.com/mcp?utm_source=allmcps&utm_medium=mcp_directory&utm_campaign=mcp_directory_2026_08&utm_content=profile"
}
}
}
Frequently asked questions
MediaWiki MCP Server is categorized under Developer Tools and uses a local stdio subprocess. Picorn MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick MediaWiki MCP Server for developer tools work and Picorn MCP for developer tools.
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.
MediaWiki MCP Server is listed as free. Picorn MCP is listed as free. 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 mediawiki-mcp-server and picorn-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MediaWiki MCP Server has a quality signal of 68/100 (Great) with 2 views, 0 installs and 136 GitHub stars. Picorn MCP has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.