Which productivity and docs MCP servers are cataloged?

14 productivity and docs MCP servers are cataloged, each with verified publisher, access, and spec-revision facts.

Which productivity and docs MCP servers support the current spec revision?

0 productivity and docs MCP servers have verified support for the current revision (2026-07-28). The rest are on earlier revisions or unverified.

Productivity and Docs MCP Servers

14 productivity and docs MCP servers are cataloged, 0 with verified current-spec support.

MCP servers for documents, tasks, and office work: document editing and conversion, spreadsheets, project trackers, calendars, and note apps.

Airtable - Earlier Revision
Distributed as npm:airtable-mcp-server. Resolved from the published package: airtable-mcp-server 1.14.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
atlassian-dc-mcp-confluence - Earlier Revision
Distributed as npm:@atlassian-dc-mcp/confluence. Resolved from the published package: @atlassian-dc-mcp/confluence 0.29.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
atlassian-dc-mcp-jira - Earlier Revision
Distributed as npm:@atlassian-dc-mcp/jira. Resolved from the published package: @atlassian-dc-mcp/jira 0.29.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
clickup - Earlier Revision
Distributed as npm:@taazkareem/clickup-mcp-server. Resolved from the published package: @taazkareem/clickup-mcp-server 0.14.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
Contentful MCP Server - Spec Support Unverified
Authority rests on the server living in the verified contentful GitHub organization, which GitHub's API reports with "is_verified": true, and on its publication under the @contentful npm scope; package.json for both workspace packages lists author "Contentful GmbH". The published package, @contentful/mcp-server, depends on a shared library, @contentful/mcp-tools, published from the same monorepo and versioned separately. No fetched page names an MCP protocol revision (README, CHANGELOG.md, and AGENTS.md were all checked); the @modelcontextprotocol/sdk ^1.26.0 dependency is a version range, not evidence of a specific revision, so spec_status is unknown. Vendor documentation on contentful.com was not verified this session: the domain returned HTTP 429 on every attempt, so authority and entity facts here rest on the GitHub org record, the README, package.json, and the advisory API rather than any contentful.com page.
Desktop Commander - Earlier Revision
MCP server giving an assistant terminal command execution, process management, and filesystem operations on the local machine, run over stdio via npx @wonderwhy-er/desktop-commander. Telemetry is on by default with a documented opt-out. No vendor documentation surface names a supported MCP revision. Resolved from the published package: @wonderwhy-er/desktop-commander 0.2.47 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
Google Drive MCP - Spec Support Unverified
Community server for Google Workspace, distributed as npm:@piotr-agier/google-drive-mcp and self-hosted by the operator. The user supplies their own Google Cloud OAuth client, so the server holds no vendor credentials of its own. No documentation names a dated MCP specification revision: the deployment guide links the draft authorization specification for its team mode, which is the draft rather than a released revision, and the package depends on @modelcontextprotocol/sdk ^1.24.0, an SDK range. Published by an individual GitHub user with no Google affiliation, so authority is community despite the product names in the title.
Google Workspace MCP (aaronsb) - Spec Support Unverified
Distributed as npm:@aaronsb/google-workspace-mcp. Community: the publisher is the personal GitHub account aaronsb and the server fronts Google Workspace, which the publisher does not operate. Requires the user's own Google OAuth credentials. No MCP revision statement found (checked 2026-08-27).
kaneo - Earlier Revision
Distributed as npm:@kaneo/mcp. Resolved from the published package: @kaneo/mcp 0.1.11 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
mcp-server-trello - Earlier Revision
Distributed as npm:@delorenj/mcp-server-trello. Resolved from the published package: @delorenj/mcp-server-trello 1.8.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
Microsoft 365 MCP Server - Earlier Revision
Distributed as npm:@softeria/ms-365-mcp-server. Resolved from the published package: @softeria/ms-365-mcp-server 0.145.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
PDF Reader MCP - Spec Support Unverified
Distributed as npm:@sylphx/pdf-reader-mcp. Renamed, recorded 2026-08-25: version 5.0.0 is a hard cut to the @sylphx/citra npm package ("Current production identity: @sylphx/citra@5.0.0" per docs/migration.md), with the project stating a new MCP identity io.github.SylphxAI/citra; the registry_name here reflects the pre-rename record. Native Rust engine behind a thin Node launcher. No MCP revision statement in README or docs (checked 2026-08-25). Authority: Sylphx is a GitHub organization (sylphx.com) and the tool is its own product.
SiYuan - Spec Support Unverified
Built-in MCP server of the SiYuan note-taking application (siyuan-note/siyuan), shipped inside the same Go kernel binary used by the desktop, server, and Docker builds; there is no separate package to install. kernel/mcp/server.go (tag v3.8.3) registers `ginServer.POST("/mcp", model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, serveHTTP(handler))`, plus matching GET and DELETE routes, as Streamable HTTP only; no stdio or SSE code path exists for this server. Auth is an API token, via an `Authorization: Token`/`Bearer` header or a `?token=` query parameter, or an existing session, gated to the Administrator role; the default tool-exposure policy found in source is allow with no overrides, so an authenticated administrator reaches the full tool set by default. The only revision-dated string found anywhere in the fetched surfaces is a source constant, `protocolVersion20260728 = "2026-07-28"`, used only to branch HTTP-handler behavior by request header; that is source code observed via static fetch, not a vendor statement, docs page, or live probe, so spec_status stays unknown. No SiYuan user-guide page for the MCP feature could be fetched: b3log.org/siyuan does not mention MCP and a guessed English-language doc path returned HTTP 404 (COULD NOT VERIFY). The v3.8.0 changelog, published 2026-08-12, announced "Support Model Context Protocol (MCP)" as a new feature, though repository security advisories show the underlying route already existed and was exploitable at v3.7.1, released 2026-07-04, over a month before that changelog entry.
Toggl MCP Server - Spec Support Unverified
Distributed as npm:@togglhq/mcp. First-party on two independent grounds: the GitHub-verified io.github.toggl namespace resolves to Toggl's verified GitHub organization, and npm lists toggl-engineering among the package maintainers. No public repository: npm carries no repository field and github.com/toggl/toggl-mcp returned 404 on 2026-08-27. Authentication is a browser sign-in flow via the server's own auth tool. No MCP revision statement found (checked 2026-08-27).