Connected Workspace MCP

A TypeScript stdio MCP server for Gmail, Google Calendar, and LinkedIn. It gives MCP-compatible assistants explicit tools for email, scheduling, 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

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 --env-file "C:\Users\you\.connected-workspace-mcp\.env"

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

MCP Host Configuration

{
  "servers": {
    "connected-workspace": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "connected-workspace-mcp",
        "--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.

Documentation

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

Tests never contact live providers or mutate real accounts.

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.