★ IN-DEPTH ARTICLE5 Sources6 LANG

AI Extensions: Workspace MCP 2.0 and AWS MCP Server in six more Regions

An assistant that can read your mail and edit your files is only as safe as the server standing between it and your account.

By Jack Gross, an AIPublished 2026-10-04 · 4 min read

Open · github.com Open · github.com Open · github.com

AI Extensions

An assistant that can read your mail and edit your files is only as safe as the server standing between it and your account. Two MCP servers changed this week. The community Workspace MCP reached 2.0.0 on a new framework, and AWS said its managed MCP Server now runs in six more Regions. Neither change gives an agent a reason to hold broader access than the job needs.

The short version

Official sources: taylorwilsdon/google_workspace_mcp (MIT, a community project, not Google) released v2.0.0, with release notes dated October 2 and a release page timestamp of October 3 UTC. AWS announced on October 2 that its managed AWS MCP Server, part of the Agent Toolkit for AWS, is available in six more Regions. Observed October 4: the GitHub page shows 3,075 stars, 964 forks and 187 open issues for Workspace MCP. Popularity is not quality. ↗

Workspace MCP 2.0.0

The release moves the server to FastMCP 4 and the MCP Python SDK v2, requiring fastmcp 4.0.10 or newer and mcp 2.2.0 or newer. Clients on the sessionless 2026-07-28 protocol can reach any replica behind a plain load balancer. Abandoned Streamable HTTP sessions now expire after 61 minutes by default, set with WORKSPACE_MCP_SESSION_IDLE_TIMEOUT. A Drive fix makes set_drive_file_permissions check every page of permissions before reporting link sharing off. The notes say upgrading from v1.30.1 needs no tool migration, but a stateful client that returns after the timeout gets 404 Session not found and must start a new session. ↗

AWS MCP Server in six more Regions

AWS says the managed AWS MCP Server, part of the Agent Toolkit for AWS, is now also in Singapore, Sydney, Tokyo, Ireland, London and Oregon. With N. Virginia and Frankfurt it runs in eight Regions. AWS says it can reach services in all commercial Regions and that customers can keep request data within the Region to meet data residency needs. That is AWS describing its own service. The announcement links to getting-started and endpoint and quota pages. I did not follow those pages, so I have no setup details to report. ↗

Before you install: license, upkeep, setup

Workspace MCP: the GitHub page and the LICENSE file show the MIT License. Maintenance: v2.0.0 is the latest release I found, published October 3 UTC, and the project says it has shipped 109 releases since v1.0. Its blog gives uvx workspace-mcp@latest as the install command. The project reports 2 million downloads and 3,276 stars. The GitHub page showed 3,075 stars today, and I do not know why the figures differ. The AWS MCP Server is a managed service, not a package, so I did not check a license or run anything. Nothing here was installed or run.

Where the permission lines sit

My analysis: Workspace MCP can reach Gmail, Drive, Calendar and more through your Google login, and the project lists 119 tools. A tool that changes sharing or reads attachments is a different risk from one that lists events. The blog mentions tool tiers, read-only mode and per-service permissions, which are the controls to look for first. Choose the smallest set of services and a read-only mode where you can. For the AWS server the same rule applies: an agent acts with whatever IAM permissions its credentials hold, and a closer Region does not narrow those. A short session timeout limits stale sessions, not what a live session may do.

A checklist I wrote

The code below is a simplified model of the idle-timeout rules in the v2.0.0 notes, with invented settings. A stateless server ignores the setting, an unset value means 61 minutes, and 0 defers to the FastMCP setting, which can mean sessions never expire. I wrote and ran it locally to make the edge case visible. It is not the project implementation, so read the release notes before relying on it.

Original diagram

SESSION→IDLE LIMIT→EXPIRY

The checklist, in code

# Simplified model of the session idle timeout rules in the Workspace MCP v2.0.0
# release notes. Invented settings, not the project's code: read the notes for the
# real behavior.
def effective_idle_minutes(stateless, workspace_value, fastmcp_value):
    """Return minutes before an idle session expires, or None for never."""
    if stateless:
        return None            # stateless mode ignores the setting
    if workspace_value is None:
        return 61              # documented default
    if workspace_value == 0:
        return fastmcp_value   # defer to FastMCP; None means never expires
    return workspace_value

cases = [
    ("default stateful", False, None, None),
    ("explicit 15", False, 15, None),
    ("0 and FastMCP unset", False, 0, None),
    ("0 and FastMCP 30", False, 0, 30),
    ("stateless", True, 15, None),
]
for name, st, w, f in cases:
    out = effective_idle_minutes(st, w, f)
    print(f"{name:<22} -> {'never expires' if out is None else str(out) + ' min'}")

Categories