Connected Workspace MCP

A TypeScript stdio MCP server for Gmail, Google Calendar, Sheets, Drive, Contacts, Tasks, and LinkedIn. It gives MCP-compatible assistants 42 explicit tools for email, scheduling, spreadsheets, files, contacts, task management, professional profile access, and social publishing.

Gmail and Calendar share one Google OAuth grant. LinkedIn uses a separate OAuth grant. Both providers persist tokens outside the package directory so the server can restart without repeated authorization.

Install

Requires Node.js 20 or newer.

npm install --global connected-workspace-mcp@1.0.2

Configure the provider credentials described in the auth guides, then run:

connected-workspace-google-auth
connected-workspace-linkedin-auth
connected-workspace-mcp

With npx, keep credentials in a private file and pass only its path:

npx -y connected-workspace-mcp@1.0.2 --env-file "C:\Users\you\.connected-workspace-mcp\.env"

LinkedIn is optional. The server can run with only Google configured.

Related MCP server: MCP Google Workspace Server

MCP Host Configuration

{
  "servers": {
    "connected-workspace": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "connected-workspace-mcp@1.0.2",
        "--env-file",
        "C:\\Users\\you\\.connected-workspace-mcp\\.env"
      ]
    }
  }
}

The process can instead inherit provider environment variables directly. Never pass client secrets or tokens as command-line arguments.

On Windows, use npx.cmd if your host cannot launch npx. For the Add MCP Server form, select Local, set the command to npx.cmd, leave environment variables empty, use a 120-second timeout, and paste these arguments for a private environment file at D:\environment-file\.env:

[
  "-y",
  "connected-workspace-mcp@1.0.2",
  "--env-file",
  "D:\\environment-file\\.env"
]

No source checkout or local build is required. Authorize Google once using the installed executable or npm exec as shown in the usage guide. If npm cannot find the version or reports missing SDK files, see npm troubleshooting.

Documentation

• Consumer examples and minimal environment setup

• Documentation index

• Installation and MCP host setup

• Google OAuth setup

• LinkedIn OAuth setup

• Configuration, token storage, and logs

• Tool reference

• Authentication troubleshooting

• npm publishing guide

Capabilities

Gmail tools search and read messages, send new messages, reply in threads, and modify labels. Calendar tools list, create, update, and delete events, and query free/busy periods. Sheets tools read, write, append, and clear spreadsheet data. Drive tools find, copy, share, and trash files and create folders. Contacts and Tasks tools manage Google contacts and task lists. All Google tools share the same OAuth client. LinkedIn tools read the authenticated profile and posts, inspect available engagement, publish text or image posts, and delete owned posts.

Standard LinkedIn APIs do not support arbitrary edits to profile fields such as headline, experience, or skills. Available endpoints depend on the products and permissions approved for the LinkedIn app.

Local Development

npm install
Copy-Item .env.example .env
npm run auth:google
npm run auth:linkedin
npm run build
npm start

Run the deterministic mocked test suite and project checks with:

npm test
npm run check
npm run format:check
npm run test:package

Tests never contact live providers or mutate real accounts. The package check installs a temporary tarball with production dependencies and verifies all three executables and MCP tool discovery.

Publishing To npm

The Release and Publish workflow publishes a stable version when a GitHub Release is published. It can also be started manually from the Actions tab with a version matching package.json.

1. Create an npm granular access token with permission to publish connected-workspace-mcp and permission to bypass 2FA for automation.

2. Save it as the repository Actions secret NPM_AUTH_TOKEN. Do not put this token in .env.example, source files, or MCP host configuration.

3. Commit and push the version bump, then create a GitHub Release with the matching tag, for example v1.0.1.

The workflow rejects mismatched or already-published versions, runs tests, type/build/format checks, audits dependencies, tests an installed tarball, and publishes with npm provenance. It then verifies the version on npm. Publishing a prerelease GitHub Release does not publish to the latest npm tag. If npm processing delays visibility, use the workflow's verify_only option to recheck the submitted version without publishing it again.

See the publishing guide for commands, token setup, manual runs, and rollback instructions.

Contributing

Contributions are welcome. Read CONTRIBUTING.md for project structure, security requirements, validation commands, and pull-request guidance.

Security

Never commit .env, token files, or logs. The JSON-lines logger excludes tool arguments, message bodies, post content, and credentials. Configure your MCP host to require confirmation before write tools send email, modify calendars, or publish and delete LinkedIn posts.

License

Licensed under the MIT License.