Kordoc vs Google Workspace MCP

A side-by-side look at the Kordoc and Google Workspace MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Kordoc logoKordocWorkplace & ProductivityParse Korean documents (HWP, HWPX, PDF, XLSX, DOCX, PPTX) to Markdown; fill forms, diff, render.49FairAuth: no auth requiredGoogle Workspace MCP logoGoogle Workspace MCPWorkplace & Productivity · Local subprocess (stdio)Comprehensive Google Workspace MCP server with full support for Google Calendar, Drive, Gmail, and Docs, Forms, Chats, Slides and Sheets over stdio, Streamable HTTP and SSE transports.68GreatAuth: oauth 2.0

Verdict: choose Kordoc for workplace & productivity work; choose Google Workspace MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Kordoc logoChoose Kordoc when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: KORDOC_OFFLINE.
Explore Kordoc

Google Workspace MCP logoChoose Google Workspace MCP when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like start_google_auth, search_gmail_messages, get_gmail_message_content.
Explore Google Workspace MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKordoc logoKordocGoogle Workspace MCP logoGoogle Workspace MCP
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal49/100 · Fair68/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredOAuth 2.0
PricingFreeFree
Required env varsKORDOC_OFFLINENone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,6253,381
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed123

Tools & capabilities

Kordoc tools

No tool names declared yet. Check the project README from the listing page.

Google Workspace MCP tools 123

  • start_google_authManually initiate Google OAuth authentication flow. NOTE: This is a legacy OAuth 2.0 tool and is disabled when OAuth 2.1 is enabled. The authentication system automatically handles credential checks and prompts for authentication when needed. Only use this tool if: 1. You need to re-authenticate with different credentials 2. You want to proactively authenticate before using other tools 3. The automatic authentication flow failed and you need to retry In most cases, simply try calling the Google Workspace tool you need - it will automatically handle authentication if required.
  • search_gmail_messagesSearches messages in a user's Gmail account based on a query. Returns both Message IDs and Thread IDs for each found message, along with Gmail web interface links for manual verification. Supports pagination via page_token parameter.
  • get_gmail_message_contentRetrieves the full content (subject, sender, recipients, body) of a specific Gmail message. Bodies are returned inline and truncated at 20,000 characters. Set full=True to get the complete, untruncated message instead: it is exported to disk and the response carries a short-lived download URL (HTTP transport) or file path (stdio transport) rather than the body, so large messages never stream through the model context. Stateless deployments have no file storage, so there full=True returns the untruncated body inline.
  • get_gmail_messages_content_batchRetrieves the content of multiple Gmail messages in a single batch request. Supports up to 25 messages per batch to prevent SSL connection exhaustion.
  • get_gmail_attachment_contentDownloads an email attachment and saves it to local disk. In stdio mode, returns the local file path for direct access. In HTTP mode, returns a temporary download URL (valid for 1 hour). May re-fetch message metadata to resolve filename and MIME type.
  • send_gmail_messageSends an email using the user's Gmail account. Supports new emails, replies, and forwards, with optional attachments. Supports Gmail's "Send As" feature to send from configured alias addresses. To forward an existing message, pass forward_message_id. The original subject, body (quoted with a "Forwarded message" header), and attachments are carried over. In forward mode, body (if any) is prepended as a note and subject is optional. Threading, reply, and signature options do not apply when forwarding. THIS TOOL SENDS IMMEDIATELY AND CANNOT SCHEDULE. Gmail's REST API exposes no send-time parameter; Schedule send is a web-UI feature with no API equivalent, so no argument to this tool can defer delivery. Never tell a user a message was scheduled. For "prepare now, deliver later", create a draft with draft_gmail_message. An external scheduler must retain the message data to create and send a new message via send_gmail_message at the chosen time, or call users.drafts.send with the draft ID returned by draft_gmail_message. Alternatively, let the user schedule that draft in the Gmail UI.
  • draft_gmail_messageCreates a draft email in the user's Gmail account. Supports both new drafts and reply drafts with optional attachments. Supports Gmail's "Send As" feature to draft from configured alias addresses. SCHEDULED SEND IS NOT AVAILABLE. Gmail's REST API exposes no send-time parameter; the Schedule send feature is web-UI only, and a message cannot be placed in the Scheduled folder through the API. Do not claim a message was scheduled. To deliver at a chosen time, create a draft with draft_gmail_message. An external scheduler must retain the message data to create and send a new message via send_gmail_message then, or call users.drafts.send with the draft ID returned by draft_gmail_message. Alternatively, let the user schedule the draft in the Gmail UI.
  • get_gmail_thread_contentRetrieves the complete content of a Gmail conversation thread, including all messages. Optionally also returns structured ownership analysis so a caller can determine who sent the last message and who owes whom a response without re-parsing the formatted string or making a second tool call.
  • get_gmail_threads_content_batchRetrieves the content of multiple Gmail threads in a single batch request. Supports up to 25 threads per batch to prevent SSL connection exhaustion.
  • list_gmail_labelsLists labels in the user's Gmail account.
  • manage_gmail_labelManages Gmail labels: create, update, or delete labels.
  • list_gmail_filtersLists all Gmail filters configured in the user's mailbox.
  • +111 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.

Kordoc

No confirmed install command for Kordoc yet — follow the setup steps linked from its listing page rather than a guessed package name.

Google Workspace MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "taylorwilsdon-google-workspace-mcp": {
      "command": "uvx",
      "args": [
        "workspace-mcp"
      ]
    }
  }
}

Frequently asked questions

Kordoc is categorized under Workplace & Productivity and uses an install path we have not confirmed yet. Google Workspace MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Kordoc for workplace & productivity work and Google Workspace MCP for workplace & productivity.

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. Kordoc has no confirmed install command yet — follow its own setup instructions.

Kordoc is listed as free. Auth: no auth required. Google Workspace MCP is listed as free. Auth: oauth 2.0. 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 kordoc and taylorwilsdon-google-workspace-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Kordoc has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 2,625 GitHub stars. Google Workspace MCP has 68/100 (Great) with 4 views, 0 installs and 3,381 GitHub stars.