What is the key difference between Ve Gws and Keepsake MCP?

Ve Gws belongs to the Workplace & Productivity category with local stdio execution, while Keepsake MCP belongs to the Workplace & Productivity category with local stdio execution.

How do I install Ve Gws or Keepsake MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Ve Gws and Keepsake MCP free or paid?

Ve Gws operates under a Free / Open Source model (OAuth 2.0). Keepsake MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Ve Gws lists 123 tools with 1 views and 2 GitHub stars. Keepsake MCP lists 73 tools with 2 views and 1 GitHub stars.

Can I use both Ve Gws and Keepsake MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Ve Gws vs Keepsake MCP

In-depth architectural comparison of the Ve Gws and Keepsake MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Ve Gws

Workplace & Productivity · Local stdio

Quality: 56/100 (Good) | Auth: OAuth 2.0

Keepsake MCP

Workplace & Productivity · Local stdio

Quality: 59/100 (Good) | Auth: API Key required

Verdict Summary: Choose Ve Gws if you need specialized Workplace & Productivity tools running via a local process. Choose Keepsake MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Ve Gws when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
Primary tools included: start_google_auth, search_gmail_messages, get_gmail_message_content.

Explore Ve Gws Details

Choose Keepsake MCP when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: KEEPSAKE_API_KEY.
Primary tools included: list_contacts, get_contact, create_contact.

Explore Keepsake MCP Details

Feature & Specification Comparison

Specification	Ve Gws HuntsDesk Workplace & Productivity	Keepsake MCP nicolascroce Workplace & Productivity
Summary	VE Google Workspace MCP. Fork of taylorwilsdon/googleworkspacemcp with 28 authoring-focused tools on top (deeper Slides automation, native markdown-to-Docs rendering with smart chips, Sheets data validation + named ranges + range protection, recursive Drive folder copy, revision history). 822 tests pass. Companion to HuntsDesk/ve-kit.	Personal CRM — manage contacts, interactions, tasks, notes, daily journal, and tags through 42 MCP tools
Category & Scope

Tools & Capabilities Breakdown

Ve Gws Tools (123)

start_google_auth

Manually 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_messages

Searches 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_content

Retrieves 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.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Ve Gws Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "huntsdesk-ve-gws": {
      "command": "uvx",
      "args": [
        "workspace-mcp"
      ]
    }
  }
}

Keepsake MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "nicolascroce-keepsake-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "keepsake-mcp"
      ],
      "env": {
        "KEEPSAKE_API_KEY": "YOUR_KEEPSAKE_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Ve Gws is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Keepsake MCP belongs to Workplace & Productivity using local stdio subprocess. Select Ve Gws when you need capabilities focused on workplace & productivity and Keepsake MCP when you require tools for workplace & productivity.

More alternatives to Ve Gws More alternatives to Keepsake MCP Workplace & Productivity category hub